[Touch-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
Here is one method to see the dialog without working remotely: sudo sed 's/yes/auth_self/' -i /usr/share/polkit-1/actions/org.freedesktop.accounts.policy Then press Alt+Ctrl+F2 to switch to vt2, and Alt+Ctrl+F7 to switch back to vt7. After testing, to revert the change, run: sudo sed 's/auth_self/yes/' -i /usr/share/polkit-1/actions/org.freedesktop.accounts.policy On LTSP thin clients, one can reproduce it by just changing VTs, without changing the accountsservice polkit files. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Status in policykit-1-gnome package in Ubuntu: Confirmed Bug description: Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568667] Re: apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667
and $ ubuntu-bug whoopsie usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: whoopsie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1568667 Title: apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667 Status in whoopsie package in Ubuntu: New Bug description: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 apport-collect 1568663 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568663 apport-collect 1568667 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568667 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash CurrentDesktop: GNOME Date: Mon Apr 11 09:43:08 2016 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1568667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567429] Re: Scope::settings() is too slow
** Branch linked: lp:~marcustomlinson/unity-scopes-shell/lp-1567429 ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1567429 Title: Scope::settings() is too slow Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: Evaluating settingsEnabled: scopeView.scope && scopeView.scope.settings && scopeView.scope.settings.count > 0 || false in GenericScopeView.qml takes around 300 ms when running on the phone, which basically feels like an eternity if you're trying to use the phone to scroll, change to another scope, etc If this needs heavy calculation this should be either pre-calculated and cached or calculated in a separate thread and then signalled with a signal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1567429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379535] Re: policy namespace stacking
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1379535 Title: policy namespace stacking Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial:
[Touch-packages] [Bug 1210514] Re: Default apache prefork profile doesn't allow chown
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1210514 Title: Default apache prefork profile doesn't allow chown Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Bug description: About every other day, I would see this in my kern.log: kern
[Touch-packages] [Bug 1272028] Re: remount, not honored on bind mounts
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1272028 Title: remount, not honored on bind mounts Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Precise: Expired Status in apparmor source package in Trusty: Expired Status in apparmor so
[Touch-packages] [Bug 1534405] Re: Regression in parser compiling/loading a directory
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1534405 Title: Regression in parser compiling/loading a directory Status in AppArmor: Fix Committed Status in AppArmor 2.10 series: Fix Committed Status in AppArmor master series: Fix Committed Status in apparmor package in Ubu
[Touch-packages] [Bug 1528139] Re: serialize_profile_from_old_profile() crash if file contains multiple profiles
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1528139 Title: serialize_profile_from_old_profile() crash if file contains multiple profiles Status in AppArmor: Fix Committed Status in AppArmor 2.10 series: Fix Committed Status in apparmor package in Ubuntu: Fix Released Bug des
[Touch-packages] [Bug 1561302] Re: gdm won't allow passwordless login
As documented in pam_unix(8), the nullok_secure option means that null passwords are allowed for this module only when connected via one of the "secure" (that is, generally speaking, "local") ttys listed in /etc/securetty. The tty is not determined directly by pam_unix, but is instead provided to the PAM stack by the calling application setting the PAM_TTY value with pam_set_item(). This is further documented in pam_set_item(3) to be: PAM_TTY The terminal name: prefixed by /dev/ if it is a device file; for graphical, X-based, applications the value for this item should be the $DISPLAY variable. If gdm is not setting the PAM_TTY item, then that's a bug in gdm, not in PAM. The /etc/securetty list of values is regrettably not comprehensive (because e.g. it doesn't support pattern matching), so if your system has been changed to run gdm on an X display beyond :3, the default value will not work for you. However, I don't see any reason this would occur unless the settings of gdm itself had been changed away from the defaults, and if you've done this you will need to adjust the contents of /etc/securetty to match. ** Changed in: pam (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1561302 Title: gdm won't allow passwordless login Status in gdm: Confirmed Status in Ubuntu GNOME: Triaged Status in casper package in Ubuntu: New Status in gdm3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: New Status in pam package in Ubuntu: Invalid Bug description: The Live session user does not have a password set, however gdm won't allow login in this case since the "Sign In" button is disabled. Normally this should be too much of an issue, since the login screen should only be hit on logout from the live session, some people are reporting hitting the gdm login screen on boot due to ubiquity-dm failing to boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gdm3 3.18.2-1ubuntu1 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: GNOME Date: Thu Mar 24 13:55:19 2016 InstallationDate: Installed on 2016-03-23 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1561302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525119] Re: Cannot permit some operations for sssd
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1525119 Title: Cannot permit some operations for sssd Status in AppArmor: Fix Committed Status in AppArmor 2.10 series: Fix Committed Status in AppArmor 2.9 series: Fix Committed Status in apparmor package in Ubuntu: Fix Release
[Touch-packages] [Bug 1501913] Re: Apparmor Abstraction Prevents Firefox From Opening Torrents in Deluge-Gtk
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1501913 Title: Apparmor Abstraction Prevents Firefox From Opening Torrents in Deluge-Gtk Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Fix Released Bug description: The apparmor abstractions in ubuntu-b
[Touch-packages] [Bug 1540562] Re: aa-genprof crashes in logparser NoneType has no "replace"
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1540562 Title: aa-genprof crashes in logparser NoneType has no "replace" Status in AppArmor: Fix Committed Status in AppArmor 2.10 series: Fix Committed Status in AppArmor 2.9 series: Fix Committed Status in apparmor package in Ubuntu
[Touch-packages] [Bug 1541914] Re: passwd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14
This bug was fixed in the package upstart - 1.13.2-0ubuntu21 --- upstart (1.13.2-0ubuntu21) xenial; urgency=medium * init/tests/test_job_process.c: Relax assertion about output format of "dd", as it changed recently. Fixes test failure and FTBFS. * init/tests/test_job_process.c: Disable "exited with signal" check in "with single-line script that is killed" test, as this is racy: it is possible that a short lived process exits faster than we manage to kill it. This will enable us to un-ignore autopkgtests again. -- Martin Pitt Mon, 29 Feb 2016 16:06:05 +0100 ** Changed in: upstart (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1541914 Title: passwd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14 Status in upstart package in Ubuntu: Fix Released Bug description: Upgrading a 14.04 machine to 16.04 in the QA Jenkins we see this message. Hopefully useful log extracts: Setting up libpam-modules:amd64 (1.1.8-3.1ubuntu3) ... dpkg: dependency problems prevent configuration of passwd: passwd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14. dpkg: error processing package passwd (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of libuuid1:amd64: libuuid1:amd64 depends on passwd; however: Package passwd is not configured yet. dpkg: error processing package libuuid1:amd64 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of libblkid1:amd64: libblkid1:amd64 depends on libuuid1 (>= 2.16); however: Package libuuid1:amd64 is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1541914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561762] Re: [FFe] AppArmor 2.11 Beta 1 for policy namespace stacking and bug fixes
This bug was fixed in the package apparmor - 2.10.95-0ubuntu1 --- apparmor (2.10.95-0ubuntu1) xenial; urgency=medium * Update to apparmor 2.10.95 (2.11 Beta 1) (LP: #1561762) - Allow Apache prefork profile to chown(2) files (LP: #1210514) - Allow deluge-gtk and deluge-console to handle torrents opened in browsers (LP: #1501913) - Allow file accesses needed by some programs using libnl-3-200 (Closes: #810888) - Allow file accesses needed on systems that use NetworkManager without resolvconf (Closes: #813835) - Adjust aa-status(8) to work without python3-apparmor (LP: #1480492) - Fix aa-logprof(8) crash when operating on files containing multiple profiles with certain rules (LP: #1528139) - Fix log parsing crashes, in the Python utilities, caused by certain file related events (LP: #1525119, LP: #1540562) - Fix log parsing crasher, in the Python utilities, caused by certain change_hat events (LP: #1523297) - Improve Python 2 support of the utils by fixing an aa-logprof(8) crasher when Python 3 is not available (LP: #1513880) - Send aa-easyprof(8) error messages to stderr instead of stdout (LP: #1521400) - Fix aa-autodep(8) failure when the shebang line of a script contained parameters (LP: #1505775) - Don't depend on the system logprof.conf when running utils/ build tests (LP: #1393979) - Fix apparmor_parser(8) bugs when parsing profiles that use policy namespaces in the profile declaration or profile transition targets (LP: #1540666, LP: #1544387) - Regression fix for apparmor_parser(8) bug that resulted in the --namespace-string commandline option being ignored causing profiles to be loaded into the root policy namespace (LP: #1526085) - Fix crasher regression in apparmor_parser(8) when the parser was asked to process a directory (LP: #1534405) - Fix bug in apparmor_parser(8) to honor the specified bind flags remount rules (LP: #1272028) - Support tarball generation for Coverity scans and fix a number of issues discovered by Coverity - Fix regression test failures on s390x systems (LP: #1531325) - Adjust expected errno values in changeprofile regression test (LP: #1559705) - The Python utils gained support for ptrace and signal rules - aa-exec(8) received a rewrite in C - apparmor_parser(8) gained support for stacking multiple profiles, as supported by the Xenial kernel (LP: #1379535) - libapparmor gained new public interfaces, aa_stack_profile(2) and aa_stack_onexec(2), allowing applications to utilize the new kernel stacking support (LP: #1379535) * Drop the following patches since they've been incorporated upstream: - aa-status-dont_require_python3-apparmor.patch - r3209-dnsmasq-allow-dash - r3227-locale-indep-capabilities-sorting.patch - r3277-update-python-abstraction.patch - r3366-networkd.patch, - tests-fix_sysctl_test.patch - parser-fix-cache-file-mtime-regression.patch - parser-verify-cache-file-mtime.patch - parser-run-caching-tests-without-apparmorfs.patch - parser-do-cleanup-when-test-was-skipped.patch - parser-allow-unspec-in-network-rules.patch * debian/rules, debian/apparmor.install, debian/apparmor.manpages: Update for new upstream binutils directory and aa-enabled binary - Continue installing aa-exec into /usr/sbin/ for now since click-apparmor's aa-exec-click autopkgtest expects it to be there * debian/libapparmor-dev.manpages: Include the new aa_stack_profile.2 man page * debian/patches/r3424-nscd-profile-allow-paranoia-mode.patch: Allow file access needed for nscd's paranoia mode * debian/patches/r3425-adjust-stacking-tests-version-check.patch: Adjust the regression test build time checks, for libapparmor stacking support, to look for the 2.10.95 versioning rather than 2.11 * debian/patches/r3426-allow-debugedit-to-work-on-apparmor-parser.patch: Remove extra slash in the parser Makefile so that debugedit(8) can work on apparmor_parser(8) (LP: #1561939) * debian/patches/allow-stacking-tests-to-use-system.patch: Adjust the file rules of the new stacking tests so that the generated profiles allow the system binaries and libraries to be tested * debian/libapparmor1.symbols: update symbols file for added symbols in libapparmor -- Tyler Hicks Sat, 09 Apr 2016 01:35:25 -0500 ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1561762 Title: [FFe] AppArmor 2.11 Beta 1 for policy namespace stacking and bug fixes Status in apparmor package in Ubuntu: Fix Released Bug description: The upstream AppArmor project has cut the 2.11 Beta 1 release. It conta
[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()
Hi, could you please attach the contents of the file /var/log/lxc/(container).log as Serge suggested. That would be great. -- 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/1567037 Title: lxc-attach crashed with SIGSEGV in get_pty_on_host() Status in lxc package in Ubuntu: Fix Committed Bug description: Installed unity8-lxc, ran unity8-setup, then rebooted. Login to unity8 lxc session failed (somehow nothing happened), then I logged into Unity7 and the crash happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: lxc1 2.0.0~rc15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 6 20:11:34 2016 ExecutablePath: /usr/bin/lxc-attach InstallationDate: Installed on 2015-12-03 (124 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x563ee5318994 : movl $0x1,0x1c(%r14) PC (0x563ee5318994) ok source "$0x1" ok destination "0x1c(%r14)" (0x001c) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: lxc Stacktrace: #0 0x563ee5318994 in main () No symbol table info available. StacktraceTop: main () ThreadStacktrace: . Thread 1 (Thread 0x7fe20540f840 (LWP 2993)): #0 0x563ee5318994 in main () No symbol table info available. Title: lxc-attach crashed with SIGSEGV in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1567037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
** Description changed: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. - Version: unity8.11+16.04.201602.16.1 - Version of Mir : 0.20.1 + Version: unity8.12+16.04.201604.01.1 + Version of Mir : 0.21 -- 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/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568663] Re: Errors were encountered while processing: initramfs-tools
Here is some more: update-initramfs: deferring update (trigger activated) Setting up mousepad (0.3.0-2) ... Processing triggers for initramfs-tools-ubuntu-touch (0.72) ... Processing triggers for initramfs-tools (0.103ubuntu4.3) ... dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_4WyiK4/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for menu (2.1.46ubuntu1) ...E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1568663 Title: Errors were encountered while processing: initramfs-tools Status in initramfs-tools package in Ubuntu: New Bug description: Processing triggers for initramfs-tools (0.103ubuntu4.3) ... dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_XxdFWv/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.3 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 11 09:39:42 2016 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2016-03-12T12:57:56.952025 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1568663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568667] Re: apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660
Finally I collected the app-report using apport-cli. ** Description changed: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 + + apport-collect 1568663 + usage: whoopsie-upload-all [-h] [-t TIMEOUT] + whoopsie-upload-all: error: unrecognized arguments: 1568663 + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash CurrentDesktop: GNOME Date: Mon Apr 11 09:43:08 2016 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660 + apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667 ** Description changed: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 apport-collect 1568663 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568663 + + apport-collect 1568667 + usage: whoopsie-upload-all [-h] [-t TIMEOUT] + whoopsie-upload-all: error: unrecognized arguments: 1568667 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash CurrentDesktop: GNOME Date: Mon Apr 11 09:43:08 2016 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1568667 Title: apport-collect 1568667, whoopsie-upload-all: error: unrecognized arguments: 1568667 Status in whoopsie package in Ubuntu: New Bug description: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 apport-collect 1568663 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568663 apport-collect 1568667 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568667 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash CurrentDesktop: GNOME Date: Mon Apr 11 09:43:08 2016 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1568667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542696] Re: 16.04 LTS Xenial Xerus does not reboot properly
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1542696 Title: 16.04 LTS Xenial Xerus does not reboot properly Status in systemd package in Ubuntu: Expired Bug description: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Codename: xenial Installed it today and fully updated but it always gets stuck on reboot, even after installation finished and I got to the part "please remove installation media and press ENTER" it didnt work, I had to turn off my laptop, every reboot gets stuck, I get a splash like it is rebooting but it just stays like that, when I press a key to see console output it says something like "starting reboot", when I switch to a virtual console in an attempt to try a manual reboot, I cant even login, prompt for login is not responding to typing, nothing shows there. last -5 reboot shutdown root reboot system boot 4.4.0-2-generic Sat Feb 6 19:23 still running reboot system boot 4.4.0-2-generic Sat Feb 6 17:59 still running reboot system boot 4.4.0-2-generic Sat Feb 6 17:46 - 17:57 (00:11) wtmp begins Sat Feb 6 17:46:02 2016 How can I debug this further? Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 228-5ubuntu3 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: Unity Date: Sat Feb 6 19:37:05 2016 InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) MachineType: ASUSTeK Computer Inc. N61Da ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=54d21952-4601-4641-b958-9a7ac2b9acb1 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N61Da.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N61Da 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.:bvrN61Da.208:bd08/23/2010:svnASUSTeKComputerInc.:pnN61Da:pvr1.0:rvnASUSTeKComputerInc.:rnN61Da:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N61Da dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1542696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568660] Re: Errors were encountered while processing: initramfs-tools
*** This bug is a duplicate of bug 1568663 *** https://bugs.launchpad.net/bugs/1568663 ** This bug has been marked a duplicate of bug 1568663 Errors were encountered while processing: initramfs-tools -- 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/1568660 Title: Errors were encountered while processing: initramfs-tools Status in initramfs-tools package in Ubuntu: New Bug description: dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_XxdFWv/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1568660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568662] Re: apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660
*** This bug is a duplicate of bug 1568667 *** https://bugs.launchpad.net/bugs/1568667 ** This bug has been marked a duplicate of bug 1568667 apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1568662 Title: apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660 Status in whoopsie package in Ubuntu: New Bug description: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1568662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568663] [NEW] Errors were encountered while processing: initramfs-tools
Public bug reported: Processing triggers for initramfs-tools (0.103ubuntu4.3) ... dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_XxdFWv/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.3 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 11 09:39:42 2016 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2016-03-12T12:57:56.952025 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1568663 Title: Errors were encountered while processing: initramfs-tools Status in initramfs-tools package in Ubuntu: New Bug description: Processing triggers for initramfs-tools (0.103ubuntu4.3) ... dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_XxdFWv/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.3 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 11 09:39:42 2016 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2016-03-12T12:57:56.952025 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1568663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568667] [NEW] apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660
Public bug reported: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash CurrentDesktop: GNOME Date: Mon Apr 11 09:43:08 2016 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1568667 Title: apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660 Status in whoopsie package in Ubuntu: New Bug description: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CrashReports: 600:0:124:176272:2016-04-11 06:26:33.478468407 +0600:2016-04-11 06:26:36.014480956 +0600:/var/crash/initramfs-tools.0.crash CurrentDesktop: GNOME Date: Mon Apr 11 09:43:08 2016 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1568667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568662] [NEW] apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660
Public bug reported: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Description changed: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 + + lsb_release -rd + Description: Ubuntu 14.04.4 LTS + Release: 14.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1568662 Title: apport-collect 1568660, whoopsie-upload-all: error: unrecognized arguments: 1568660 Status in whoopsie package in Ubuntu: New Bug description: apport-collect 1568660 usage: whoopsie-upload-all [-h] [-t TIMEOUT] whoopsie-upload-all: error: unrecognized arguments: 1568660 lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1568662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568660] [NEW] Errors were encountered while processing: initramfs-tools
Public bug reported: dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_XxdFWv/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1568660 Title: Errors were encountered while processing: initramfs-tools Status in initramfs-tools package in Ubuntu: New Bug description: dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit dpkg: warning: version 'initrd.img-3.13.0-79-generic' has bad syntax: version number does not start with digit update-initramfs: Generating /boot/initrd.img-initrd.img-3.13.0-79.123-generic dpkg: warning: version 'initrd.img-3.13.0-79.123-generic' has bad syntax: version number does not start with digit grep: /boot/config-initrd.img-3.13.0-79.123-generic: No such file or directory WARNING: missing /lib/modules/initrd.img-3.13.0-79.123-generic Device driver support needs thus be built-in linux image! depmod: FATAL: initrd.img-3.13.0-79.123-generic: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_XxdFWv/lib/modules/3.13.0-79-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1568660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568656] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()
*** This bug is a duplicate of bug 1553358 *** https://bugs.launchpad.net/bugs/1553358 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1553358, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1568656/+attachment/4632108/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1568656/+attachment/4632109/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1568656/+attachment/4632111/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1568656/+attachment/4632112/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1568656/+attachment/4632113/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1568656/+attachment/4632114/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1568656/+attachment/4632115/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1553358 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libopenobex in Ubuntu. https://bugs.launchpad.net/bugs/1568656 Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal() Status in libopenobex package in Ubuntu: New Bug description: - ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libopenobex2 1.7.1-5 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Apr 10 18:41:17 2016 Dependencies: gcc-6-base 6-20160405-0ubuntu1 libc6 2.23-0ubuntu2 libgcc1 1:6-20160405-0ubuntu1 libudev1 229-4ubuntu1 libusb-1.0-0 2:1.0.20-1 ExecutablePath: /usr/sbin/obex-check-device InstallationDate: Installed on 2016-03-16 (25 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/sbin/obex-check-device 0bda ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f4224bef994 <__GI_strtoul_l_internal+68>: movsbq (%r14),%rax PC (0x7f4224bef994) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libopenobex StacktraceTop: __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f4224f79420 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 main () Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: Upgraded to xenial on 2016-03-29 (12 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1568656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551150] Re: devel-proposed - android lxc container fails to start
Still the latest arale-devel image-r303 is broken that fails to boot the phone -- 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/1551150 Title: devel-proposed - android lxc container fails to start Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. Device tarballs between 446 and 447 are the same. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 299039] Re: the recently used filenames should be ellipsized
** Changed in: gtk Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/299039 Title: the recently used filenames should be ellipsized Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Binary package hint: evince There are no items in 'File' menu after opening a file or a number of files with large name or path. It is better to implement crop of names in this menu; something like 'A very large file_na...'. Screenshot is attached. ProblemType: Bug Architecture: i386 Date: Mon Nov 17 15:37:31 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: fglrx Package: evince 2.22.2-0ubuntu2 PackageArchitecture: i386 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/299039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Confirmed ** Changed in: mir (Ubuntu) Importance: Undecided => High -- 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/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.11+16.04.201602.16.1 Version of Mir : 0.20.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553328] Re: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref()
Done. There doesn't appear to be any way that Mir itself can screw up that call. It's possible qtmir might be messing up with an incorrect 'this' pointer to the Mir DisplayBuffer. But I think much more likely that it's a nouveau driver bug. If it wasn't then we'd be seeing similar crashes with intel and radeon, but we don't. ** Changed in: libdrm (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref() Status in Mir: Invalid Status in libdrm package in Ubuntu: New Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Incomplete Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1553328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553328] Re: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref()
We should sanity-check the correctness of the eglMakeCurrent call in Mir src/server/graphics/nested/display_buffer.cpp:62 But other than that, it seems to be purely a nouveau bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref() Status in Mir: Invalid Status in libdrm package in Ubuntu: New Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Incomplete Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1553328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] Right edge switcher stutters badly with only a few apps opened
** Also affects: mir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] Right edge switcher stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in Mir: New Status in QtMir: New Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520154] Re: /etc/os-release should contain "codename" (like DISTRIB_CODENAME in lsb_release)
os-release now contains UBUNTU_CODENAME. ubuntu@localhost:~$ cat /etc/os-release NAME="Ubuntu" VERSION="16.04 (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; UBUNTU_CODENAME=xenial I'm marking this as fix released. Ogra, will this trigger the removal of lsb_release? Or what else should we do now here? ** Changed in: snappy Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1520154 Title: /etc/os-release should contain "codename" (like DISTRIB_CODENAME in lsb_release) Status in Snappy: Fix Released Status in base-files package in Ubuntu: Fix Released Bug description: to use os-release instead of lsb_release (which adds a python dependency to the snappy image and is effectively duplication of functionality) /etc/os-release should contain "codename", since the value is needed for various container operations (lxd,docker) to obtain images To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1520154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567993] Re: alsa-utils does not store and restore alsa settings on boot reboot
** Branch linked: lp:~ubuntu-audio-dev/alsa-utils/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1567993 Title: alsa-utils does not store and restore alsa settings on boot reboot Status in alsa-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: The standard run level seems to have changed from run level 2 to run level 5 in 16.04. /etc/init.d/alsa-utils does not have a symlink in rc5.d and so does not run and store and restore alsa settings on shutdown/boot. Most internal audio interfaces are set to some reasonable level by pulse on login. However, some (semi)pro audio interfaces like the ice1712 based interfaces are not controlled by pulseaudio but just fed audio in. This means that the user has to reset the alsa level at every boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-utils 1.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-lowlatency 4.4.6 Uname: Linux 4.4.0-17-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 8 07:56:32 2016 InstallationDate: Installed on 2016-03-24 (14 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1567993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556160] Re: Installed binaries fail to run with mir_demo_server --test-client XXXX
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1556160 Title: Installed binaries fail to run with mir_demo_server --test-client Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Running with the installed, or a locally built mir server the installed clients fail, and the locally built ones work. (This happens with all 22 clients, but I illustrate with mir_demo_client_basic.) (I have xenial/amd64/Mir-0.20.1 installed and trunk built locally) $ mir_demo_server --test-timeout 3 --test-client mir_demo_client_basic ... [2016-03-11 15:36:27.783743] server_example_test_client.cpp: Failed to execute client ... $ bin/mir_demo_server --test-timeout 3 --test-client mir_demo_client_basic ... [2016-03-11 15:37:38.893891] server_example_test_client.cpp: Failed to execute client $ mir_demo_server --test-timeout 3 --test-client bin/mir_demo_client_basic ... Connected Surface created Surface released Connection released [2016-03-11 15:38:31.039003] mirserver: Stopping Segmentation fault (core dumped) $ bin/mir_demo_server --test-timeout 3 --test-client bin/mir_demo_client_basic ... Connected Surface created Surface released Connection released [2016-03-11 15:39:43.230826] mirserver: Stopping To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1556160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556210] Re: Mir-on-X11 doesn't exit (until it gets an event)
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1556210 Title: Mir-on-X11 doesn't exit (until it gets an event) Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: $ bin/mir_demo_server --test-client bin/mir_demo_client_eglplasma ... Mir chose pixel format 3. Using pixel format 4. Current active output is 1280x1024 +0+0 Surface 0 DPI Surface exposed Signal 15 received. Good night. [2016-03-11 17:27:40.987963] mirserver: Stopping It sits here with a blank window until (e.g.) the cursor moves over the Mir-on-X11 window To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1556210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543049] Re: InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works breaks with old input drivers present
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1543049 Title: InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works breaks with old input drivers present Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: When there is a bump in the graphics platform ABI but no simultaneous bump in the input side we end up having more usable X11 platforms than expected. Because of the bump we get two x11 server modules: $ ls lib/server-modules/ graphics-android.so.7 graphics-dummy.so graphics-mesa-kms.so.8 input-evdev.so.4 input-stub.so server-mesa-x11.so.8 graphics-android.so.8 graphics-mesa-kms.so.7 graphics-throw.so input-evdev.so.5 server-mesa-x11.so.7 And as the log shows both are supported as input platforms (but only one would work as a graphics platform): $ bin/mir_unit_tests --gtest_filter=InputPlatformProbe* MIR_CLIENT_PLATFORM_PATH=bin/../lib/client-modules/ MIR_SERVER_PLATFORM_PATH=bin/../lib/server-modules/ LD_LIBRARY_PATH=bin/../lib exec=bin/mir_unit_tests.bin Running main() from main.cpp Note: Google Test filter = InputPlatformProbe* [==] Running 4 tests from 1 test case. [--] Global test environment set-up. [--] 4 tests from InputPlatformProbe [ RUN ] InputPlatformProbe.stub_platform_not_picked_up_by_default [2016-02-08 10:25:31.446023] mirserver: Selected input driver: mir:evdev-input (version: 0.20.0) [ OK ] InputPlatformProbe.stub_platform_not_picked_up_by_default (34 ms) [ RUN ] InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works [2016-02-08 10:25:31.460373] mirserver: Selected input driver: mir:x11-input (version: 0.20.0) [2016-02-08 10:25:31.462505] mirserver: Selected input driver: x11-input (version: 0.19.0) [2016-02-08 10:25:31.488286] mirserver: Selected input driver: mir:evdev-input (version: 0.20.0) /home/alan/display_server/development-branch/tests/unit-tests/input/test_input_platform_probing.cpp:149: Failure Value of: platforms Expected: has 2 elements and there exists some permutation of elements such that: - element #0 is a or derived from a N3mir5input5evdev8PlatformE, and - element #1 is a or derived from a N3mir5input1X14XInputPlatformE Actual: { 24-byte object , 24-byte object <60-94 46-04 00-00 00-00 50-94 46-04 00-00 00-00 80-DA 43-04 00-00 00-00>, 24-byte object }, which has 3 elements [ FAILED ] InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works (42 ms) [ RUN ] InputPlatformProbe.x11_input_platform_not_used_when_vt_specified [2016-02-08 10:25:31.524523] mirserver: Selected input driver: mir:evdev-input (version: 0.20.0) [ OK ] InputPlatformProbe.x11_input_platform_not_used_when_vt_specified (36 ms) [ RUN ] InputPlatformProbe.allows_forcing_stub_input_platform [2016-02-08 10:25:31.530326] mirserver: Selected input driver: mir:stub-input (version: 0.20.0) [ OK ] InputPlatformProbe.allows_forcing_stub_input_platform (5 ms) [--] 4 tests from InputPlatformProbe (117 ms total) [--] Global test environment tear-down [==] 4 tests from 1 test case ran. (118 ms total) [ PASSED ] 3 tests. [ FAILED ] 1 test, listed below: [ FAILED ] InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works 1 FAILED TEST If we have a release with a bump like this, users upgrading might end up in a problematic configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1543049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1556205 Title: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: $ bin/mir_demo_server --test-timeout 3 --test-client bin/mir_demo_client_flicker || echo FAILED ... Connected Surface created [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client terminated by signal 15 [2016-03-11 17:19:54.463779] mirserver: Stopping FAILED $ bin/mir_demo_server --test-timeout 3 --test-client bin/mir_demo_client_scroll || echo FAILED ... Connected Mir chose pixel format 3 Surface created [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client terminated by signal 15 [2016-03-11 17:21:51.922045] mirserver: Stopping FAILED I suspect these clients ignore SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1556205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556080] Re: [regression] Mir FTBFS when MIR_ENABLE_TESTS=no
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1556080 Title: [regression] Mir FTBFS when MIR_ENABLE_TESTS=no Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: cmake .. -DMIR_ENABLE_TESTS=no will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1556080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350343] Re: [regression] FTBFS with -DMIR_LINK_TIME_OPTIMIZATION=on -Duse_debflags=on
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1350343 Title: [regression] FTBFS with -DMIR_LINK_TIME_OPTIMIZATION=on -Duse_debflags=on Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Recently (I think since -r 1800) I've seen a linker error when combining -DMIR_LINK_TIME_OPTIMIZATION=on -Duse_debflags=on. Vis: Linking CXX executable ../../bin/mir_unit_tests CMakeFiles/mir_unit_tests.dir/test_variable_length_array.cpp.o (symbol from plugin): warning: memset used with constant zero length parameter; this could be due to transposed parameters `_ZThn8_N5boost16exception_detail19error_info_injectorISt9exceptionED1Ev' referenced in section `.data.rel.ro' of /tmp/cc8eKqFB.ltrans14.ltrans.o: defined in discarded section `.gnu.linkonce.t._ZN5boost16exception_detail19error_info_injectorISt9exceptionED5Ev' of CMakeFiles/mir_unit_tests.dir/frontend/test_session_mediator_mesa.cpp.o (symbol from plugin) `_ZThn8_N5boost16exception_detail19error_info_injectorISt9exceptionED0Ev' referenced in section `.data.rel.ro' of /tmp/cc8eKqFB.ltrans14.ltrans.o: defined in discarded section `.gnu.linkonce.t._ZN5boost16exception_detail19error_info_injectorISt9exceptionED0Ev' of CMakeFiles/mir_unit_tests.dir/frontend/test_session_mediator_mesa.cpp.o (symbol from plugin) /usr/bin/ld: ../../bin/mir_unit_tests: hidden symbol `.LTHUNK1.687447' isn't defined /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status tests/unit-tests/CMakeFiles/mir_unit_tests.dir/build.make:3886: recipe for target 'bin/mir_unit_tests' failed make[2]: *** [bin/mir_unit_tests] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1350343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557446] Re: The contents of debian/mir-demos.examples are out of date and useless
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1557446 Title: The contents of debian/mir-demos.examples are out of date and useless Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: We have a lot of examples in our examples folder: $ ls -1 examples/ | wc -l 79 we package a few of these: $ dpkg-query -L mir-demos | grep /usr/share/doc/mir-demos/examples /usr/share/doc/mir-demos/examples /usr/share/doc/mir-demos/examples/scroll.cpp.gz /usr/share/doc/mir-demos/examples/mir_image.h.gz /usr/share/doc/mir-demos/examples/basic.c.gz /usr/share/doc/mir-demos/examples/flicker.c.gz /usr/share/doc/mir-demos/examples/README /usr/share/doc/mir-demos/examples/graphics.h /usr/share/doc/mir-demos/examples/graphics_utils.cpp.gz I don't think this is useful to anyone. Either we should package the source for all the examples, or we should not package any of it and let folks obtain it by other means. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1557446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1544878 Title: Mir servers crash if I press the side mouse button (thumb) Status in Mir: Fix Released Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir servers crash if I press the side mouse button (thumb). There are two of them on the side of my Intellimouse Explorer 3.0. The kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8 and 9. When the crash happens I see in unity8.log: [1455268365.782990] MirSurfaceAPI: Caught exception at client library boundary (in mir_surface_release): /build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 *** Also happens with the Mir demo servers; they segfault but without a usable stack trace due to exception handling. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528110] Re: Mir On X (mesa-x11) keeps receiving mouse movement events even when not focused
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1528110 Title: Mir On X (mesa-x11) keeps receiving mouse movement events even when not focused Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir On X (mesa-x11) keeps receiving mouse movement events even when not focused. Move the mouse outside the Mir On X window and the internal cursor keeps moving. Even click outside the window and the Mir cursor in the window keeps moving. Confirmed this happens in Mir 0.17.1 and still in Mir 0.20.0 too so it's not a new problem with the new input stack. This is the log output when running sudo ./bin/mir_demo_server from a x11 terminal: [2016-02-17 08:42:39.905329] mirserver: Selected input driver: mir:x11-input (version: 0.20.0) [2016-02-17 08:42:39.938897] mirserver: Selected input driver: mir:evdev-input (version: 0.20.0) But to get to that situation probing of both platforms must succeed. That should only happen when you run a mir server as root within an x11 terminal without specifying a vt. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1528110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290345] Re: The server-side use of $MIR_SOCKET is confusing
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1290345 Title: The server-side use of $MIR_SOCKET is confusing Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: What we have now is that $MIR_SOCKET is set in DefaultServerConfiguration::the_socket_file() with the avowed intention that it is easier for children that want to know how to connect to us. However, this doesn't cover the "no-file" case - the corresponding code for that exists only in BasicServerConfiguration::launch_client(). In fact, in the "no-file" case there's no globally correct value for the socket name - a value needs to be provided for each client. When starting up DefaultConfiguration::parse_environment() looks to see if $MIR_SOCKET is set and $MIR_SERVER_HOST_SOCKET unset. In this case it set $MIR_SERVER_HOST_SOCKET with the value of $MIR_SOCKET. It would be better if $MIR_SOCKET were used to set the default for --host-socket as then setting it in a config file would override it (as currently implemented the environment variable overrides the config file). To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1290345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1517597 Title: [regression] mouse pointer support on emulator is broken Status in Client Developer Experience: New Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in Mir 0.18 series: Won't Fix Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Fix Released Status in android package in Ubuntu: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: STEPS: 1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. Wait for it to build 3. Run with ubuntu-emulator run rc-test 4. Starts up but the mouse never moves meaning you can't leave the first page of the welcome wizard EXPECTED: I expect the emulator cursor to follow the mouse cursor and be able to click on things ACTUAL: Emulator cursors stay in the top left preventing movement. As noted below F6 toggles the input mode. The pointer movement is quite slow and jerky. You also can no longer initiate an edge swipe even in trackball mode. This is a major regression from how the emulator used to perform. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539009] Re: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1539009 Title: Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse Status in Mir: Fix Released Status in Mir 0.20 series: Triaged Status in QtMir: Invalid Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Logging in to Unity8 on desktop (xenial) the mouse cursor moves glacially slow. I have to move the mouse across the whole desk to get anywhere. This is surprising given bug 1524145 shows the opposite is happening in the Mir demo servers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160122-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 Date: Thu Jan 28 18:32:27 2016 InstallationDate: Installed on 2015-12-03 (56 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551536] Re: Fullscreen clients freeze when using NBS with multiple monitors
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551536 Title: Fullscreen clients freeze when using NBS with multiple monitors Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Fullscreen clients freeze when using NBS with multiple monitors Test case: 1. mir_proving_server --display-config sidebyside --nbuffers=0 & 2. mir_demo_client_egltriangle -f & 3. Manually trigger switching to/from bypass mode using Alt+mousewheel to adjust opacity. Expected: Every time you restore full opacity, the triangle continues spinning smoothly Observed: The triangle freezes (permanently) when re-entering bypass mode. This is a manual test case I've used a lot in the past. A freeze indicates buffer starvation/deadlock -- we have not allocated enough buffers to cope with combinations of multi- monitor/bypass/framedropping simultaneously. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1551536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549152] Re: Cross compiling to wily/vivid doesn't work - E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -e /usr/bin/appstreamcli; then appstream
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1549152 Title: Cross compiling to wily/vivid doesn't work - E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -e /usr/bin/appstreamcli; then appstreamcli refresh > /dev/null; fi' Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Cross compiling to wily/vivid doesn't work - $ ./cross-compile-chroot.sh -d wily -a host -u ... E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -e /usr/bin/appstreamcli; then appstreamcli refresh > /dev/null; fi' E: Sub-process returned an error code apt update failed. Exit value: 100 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately
** Changed in: mir/0.21 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1549701 Title: Sometimes devices don't suspend - display turns back on immediately Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in Mir 0.21 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: current build number: 267 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en it happens also on arale. sometimes the screen lock timeout is not honoured and the devices don't suspend when the lock timeout expires (display doesn' t turn off) $ sudo powerd-cli list [sudo] password for phablet: System State Requests: Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1 Steps to reproduce on arale: 1. Turn on the screen 2. Touch the circular touch button at the lower part of the device 3. Press/release the power button to turn off screen 4. Release the circular touch button Expected results: The screen turns off and further on/off cycles work properly Actual results: The screen stays on and attempts to turn it off fail The touchscreen is handling the circular button and emits a key down event. When turning the screen of the touch screen device is turned off too. Mir is not aware of the touchscreen being off. So meanwhile the repeat handling kicks in and emits key events. This makes USC turn the screen back on again. The touchscreen driver does not notice that the circular button is still held. So still no release event is sent. We could fix this by: - fixing the touchscreen driver to release any touch contacts or buttons pressed, when the device is turned off (something the bluetooth stack seems to do on some devices) - sidestep the problem by making usc only react to press events as a wake trigger and make repeat and release events only reset the inactivity timer - give mir the knowledge that the disabled output also disables the touchscreen (a connection we need to be aware of to get the mapping of touch screen coordinates onto scene coordinates right), hence remove the device and thus turn of any repeat key handling attached to that device. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549359] Re: Rendering stutters when a new client establishes a connection
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1549359 Title: Rendering stutters when a new client establishes a connection Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: When there are existing clients rendering and a new client connects, rendering stutters at least on mesa-kms. To reproduce: sudo mir_demo_server --arw-file --vt1 mir_demo_client_egltriangle -m /tmp/mir_socket& mir_demo_client_basic <--- will cause stutter To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548989] Re: [regression] Mir stops receiving input after a pause/resume cycle
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1548989 Title: [regression] Mir stops receiving input after a pause/resume cycle Status in Mir: Fix Released Status in Mir 0.20 series: Invalid Status in mir package in Ubuntu: Fix Released Bug description: Mir stops receiving input after a pause/resume cycle, like when switching away and back to the VT a mir demo server is running. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1548989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546933] Re: [regression] MIR_CLIENT_PERF_REPORT is missing window/surface names
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1546933 Title: [regression] MIR_CLIENT_PERF_REPORT is missing window/surface names Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: [regression] MIR_CLIENT_PERF_REPORT is missing window/surface names. $ sudo env MIR_CLIENT_PERF_REPORT=log mir_demo_client_egltriangle Mir chose pixel format 3. Using pixel format 4. Current active output is 1920x1200 +0+0 Surface 0 DPI Surface exposed [1455787694.716178] perf: : 63.68 FPS, render time 389419.53ms, buffer lag 45.88ms (3 buffers) [1455787695.717076] perf: : 60.00 FPS, render time 0.08ms, buffer lag 49.95ms (3 buffers) [1455787696.717903] perf: : 60.00 FPS, render time 0.05ms, buffer lag 49.98ms (3 buffers) ^^^ The ": :" used to be ": window-name:" To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1546933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549226] Re: On arale; top panel drop down menu is semi-transparent and items are unreadable
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1549226 Title: On arale; top panel drop down menu is semi-transparent and items are unreadable Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in Mir 0.20 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: current build number: 255 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en The drop down menu is semi transparent and the items are difficult to read or almost invisible (eg sound controls - picture attached) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer' Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in Mir 0.20 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547015] Re: Packaged mir_unit_tests binary is not suitable for general use
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1547015 Title: Packaged mir_unit_tests binary is not suitable for general use Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: A few of the Mir unit tests use external files (i.e. dummy libraries) that are shipped as part of the mir-test-tools package. Unfortunately, the packaged mir_unit_test binary cannot find the needed files, leading to test failures. As such, the packaged mir_unit_tests binary is not currently suitable for general use: invoking "mir_unit_tests" should pass without any other extra configuration from the user. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1547015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546324] Re: x11 platform: mouse cursor moves strange
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1546324 Title: x11 platform: mouse cursor moves strange Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mouse only seems to update its position on click events. Additionally cursor movement is delayed - mir server seems to fall behind the xserver in processing events. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1546324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550432] Re: NBS (--nbuffers=0) causes software clients to crash with std::exception::what: Failed to mmap buffer 13, "Permission denied")
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1550432 Title: NBS (--nbuffers=0) causes software clients to crash with std::exception::what: Failed to mmap buffer 13, "Permission denied") Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: with both mesa-x11 and mesa-kms: $ bin/mir_demo_server --nbuffers=0 --test-client bin/mir_demo_client_multiwin ... [2016-02-26 17:30:14.600378] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_get_graphics_region): /home/alan/display_server/mir3/src/platforms/mesa/client/client_buffer.cpp(63): Throw in function {anonymous}::ShmMemoryRegion::ShmMemoryRegion(const std::shared_ptr&, int, const mir::geometry::Size&, mir::geometry::Stride, MirPixelFormat) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to mmap buffer 13, "Permission denied" [2016-02-26 17:30:14.600724] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_get_graphics_region): /home/alan/display_server/mir3/src/platforms/mesa/client/client_buffer.cpp(63): Throw in function {anonymous}::ShmMemoryRegion::ShmMemoryRegion(const std::shared_ptr&, int, const mir::geometry::Size&, mir::geometry::Stride, MirPixelFormat) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to mmap buffer 13, "Permission denied" [2016-02-26 17:30:14.601024] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_get_graphics_region): /home/alan/display_server/mir3/src/platforms/mesa/client/client_buffer.cpp(63): Throw in function {anonymous}::ShmMemoryRegion::ShmMemoryRegion(const std::shared_ptr&, int, const mir::geometry::Size&, mir::geometry::Stride, MirPixelFormat) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to mmap buffer 13, "Permission denied" To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1550432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546676] Re: EglSyncFence tests depend on android platform
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1546676 Title: EglSyncFence tests depend on android platform Status in Mir: Fix Released Status in Mir 0.20 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: If you build for MIR_PLATFORM=mesa-kms;mesa-x11 then you get build errors: CMakeFiles/mir_unit_tests.dir/graphics/test_egl_sync_fence.cpp.o: In function `EglSyncFence_can_wait_for_fence_with_timeout_Test::TestBody()': /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:100: undefined reference to `mir::graphics::EGLSyncFence::EGLSyncFence(std::shared_ptr const&)' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:101: undefined reference to `mir::graphics::EGLSyncFence::raise()' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:102: undefined reference to `mir::graphics::EGLSyncFence::wait_for(std::chrono::duration >)' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:100: undefined reference to `mir::graphics::EGLSyncFence::~EGLSyncFence()' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:100: undefined reference to `mir::graphics::EGLSyncFence::~EGLSyncFence()' CMakeFiles/mir_unit_tests.dir/graphics/test_egl_sync_fence.cpp.o: In function `EglSyncFence_can_clear_without_waiting_Test::TestBody()': /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:118: undefined reference to `mir::graphics::EGLSyncFence::EGLSyncFence(std::shared_ptr const&)' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:119: undefined reference to `mir::graphics::EGLSyncFence::raise()' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:120: undefined reference to `mir::graphics::EGLSyncFence::reset()' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:118: undefined reference to `mir::graphics::EGLSyncFence::~EGLSyncFence()' /«BUILDDIR»/mir-0.20.0+16.04.20160217.3/tests/unit-tests/graphics/test_egl_sync_fence.cpp:118: undefined reference to `mir::graphics::EGLSyncFence::~EGLSyncFence()' CMakeFiles/mir_unit_tests.dir/graphics/test_egl_sync_fence.cpp.o: In function `void __gnu_cxx::new_allocator::construct(mir::graphics::EGLSyncExtensions*)': /usr/include/c++/5/bits/shared_ptr_base.h:518: undefined reference to `mir::graphics::EGLSyncExtensions::EGLSyncExtensions()' /usr/include/c++/5/bits/shared_ptr_base.h:518: undefined reference to `mir::graphics::EGLSyncExtensions::EGLSyncExtensions()' /usr/include/c++/5/bits/shared_ptr_base.h:518: undefined reference to `mir::graphics::EGLSyncExtensions::EGLSyncExtensions()' /usr/include/c++/5/bits/shared_ptr_base.h:518: undefined reference to `mir::graphics::EGLSyncExtensions::EGLSyncExtensions()' /usr/include/c++/5/bits/shared_ptr_base.h:518: undefined reference to `mir::graphics::EGLSyncExtensions::EGLSyncExtensions()' https://launchpadlibrarian.net/240210508/buildlog_ubuntu-xenial- arm64.mir_0.20.0+16.04.20160217.3-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1546676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568576] Re: Thinkpad T460 & Ultra Dock - No audio output on dock plug
** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1568576 Title: Thinkpad T460 & Ultra Dock - No audio output on dock plug Status in alsa-driver package in Ubuntu: Incomplete Bug description: Thinkpad T460, Ultra dock, 2 channel speakers connected to dock. 4.4.0-18 Kernel / 16.04. When the laptop is docked & speakers are connected to the dock audio connector, I get no audio outpout from the dock audio connector. Looks like the same issue as reported in: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680 However the pin quirks appear to be different for the T*60 series of laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555620] Re: 'mir_demo_server --test-client' crashes (SIGSEGV) when client dies
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1555620 Title: 'mir_demo_server --test-client' crashes (SIGSEGV) when client dies Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Because the mir_demo_client_flicker doesn't install a signal handler it doesn't handle SIGTERM nicely and dies in the following scenario. This (incorrectly) crashes the server. $ bin/mir_demo_server --test-client bin/mir_demo_client_flicker ... Segmentation fault (core dumped) (Note I've MP'd a correction to mir_demo_client_flicker - so you may need to revert that to reproduce as described here.) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1555620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555708] Re: [testfail] CI failure: TestClientInput.client_input_config_request_receives_all_attached_devices
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1555708 Title: [testfail] CI failure: TestClientInput.client_input_config_request_receives_all_attached_devices Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/413/consoleFull 13:53:32 9: [ RUN ] TestClientInput.client_input_config_request_receives_all_attached_devices 13:53:32 9: [2016-03-10 13:53:32.004747] mirserver: Starting 13:53:32 9: [2016-03-10 13:53:32.007450] mirserver: Selected driver: dummy (version 0.20.0) 13:53:32 9: [2016-03-10 13:53:32.030724] mirserver: Initial display configuration: 13:53:32 9: [2016-03-10 13:53:32.032689] mirserver: 1.1: VGA 0.0" 0x0mm 13:53:32 9: [2016-03-10 13:53:32.033013] mirserver: Current mode 1000x800 60.00Hz 13:53:32 9: [2016-03-10 13:53:32.033302] mirserver: Preferred mode 1000x800 60.00Hz 13:53:32 9: [2016-03-10 13:53:32.033575] mirserver: Logical position +0+0 13:53:32 9: [2016-03-10 13:53:32.035886] mirserver: Using software cursor 13:53:32 9: [2016-03-10 13:53:32.057456] mirserver: Selected input driver: mir:stub-input (version: 0.20.0) 13:53:32 9: [2016-03-10 13:53:32.058595] mirserver: Mir version 0.20.0 13:53:32 9: /��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid426bzr3383/tests/acceptance-tests/test_client_input.cpp:780: Failure 13:53:32 9: Value of: mir_input_config_device_count(config) 13:53:32 9: Expected: is equal to 3 13:53:32 9: Actual: 0 (of type unsigned long) 13:53:32 9: /��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid426bzr3383/tests/acceptance-tests/test_client_input.cpp:782: Failure 13:53:32 9: Value of: config 13:53:32 9: Expected: a device matches ("keyboard", "keyboard-uid", 4) 13:53:32 9: Actual: 0xb43ec70 (of type MirInputConfig*) 13:53:32 9: /��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid426bzr3383/tests/acceptance-tests/test_client_input.cpp:783: Failure 13:53:32 9: Value of: config 13:53:32 9: Expected: a device matches ("mouse", "mouse-uid", 2) 13:53:32 9: Actual: 0xb43ec70 (of type MirInputConfig*) 13:53:32 9: /��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid426bzr3383/tests/acceptance-tests/test_client_input.cpp:786: Failure 13:53:32 9: Value of: config 13:53:32 9: Expected: a device matches ("touchscreen", "touchscreen-uid", 272) 13:53:32 9: Actual: 0xb43ec70 (of type MirInputConfig*) 13:53:32 9: [2016-03-10 13:53:32.538334] mirserver: Stopping 13:53:32 9: [ FAILED ] TestClientInput.client_input_config_request_receives_all_attached_devices (574 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1555708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552065] Re: [ FAILED ] DisplayConfigurationTest.output_position_is_independent_of_orientation
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1552065 Title: [ FAILED ] DisplayConfigurationTest.output_position_is_independent_of_orientation Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Failing in CI: [ FAILED ] DisplayConfigurationTest.output_position_is_independent_of_orientation https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/282/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1552065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects
** Changed in: mir Status: Fix Committed => Fix Released -- 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/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Fix Committed Status in Mir: Fix Released Status in Mir 0.20 series: Fix Released Status in bluez package in Ubuntu: Invalid Status in mir package in Ubuntu: Fix Released Bug description: Every now and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) It seems to be related somehow to bt devices disconnecting the only cure is a reboot This was reproduced by turning off the keyboard while holding down a key. We suspect the key up event is never delivered. This mimics the case where the BT connection drops off momentarily or perhaps an event is missed over the BT connection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568632] Re: evolution-addressbook-factory-subprocess crashed with SIGSEGV in xmlFindCharEncodingHandler()
*** This bug is a duplicate of bug 1545711 *** https://bugs.launchpad.net/bugs/1545711 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545711, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1568632/+attachment/4632048/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1568632/+attachment/4632050/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1568632/+attachment/4632052/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1568632/+attachment/4632053/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1568632/+attachment/4632054/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1568632/+attachment/4632056/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1568632/+attachment/4632057/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1545711 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1568632 Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in xmlFindCharEncodingHandler() Status in evolution-data-server package in Ubuntu: New Bug description: evolution-addressbook-factory-subprocess crashes sometimes Addressbooks: - Local - Google - Microsoft Exchange Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 evolution-data-server: Installiert: 3.18.5-1ubuntu1 Installationskandidat: 3.18.5-1ubuntu1 Versionstabelle: *** 3.18.5-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: evolution-data-server 3.18.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 11 01:39:28 2016 EcryptfsInUse: Yes ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess InstallationDate: Installed on 2015-09-27 (196 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2957x15 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2957/15 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANGUAGE=de_CH:de LANG=de_CH.UTF-8 Signal: 11 SourcePackage: evolution-data-server StacktraceTop: xmlFindCharEncodingHandler () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 xmlDocDumpMemory () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 e_soap_message_persist () from /usr/lib/evolution-data-server/libeews-1.2.so.0 e_ews_connection_get_folder () from /usr/lib/evolution-data-server/libeews-1.2.so.0 e_ews_connection_get_folder_sync () from /usr/lib/evolution-data-server/libeews-1.2.so.0 Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in xmlFindCharEncodingHandler() UpgradeStatus: Upgraded to xenial on 2016-03-26 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1568632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567037] Re: lxc-attach crashed with SIGSEGV in get_pty_on_host()
I did a fresh install of the latest daily build and still I am unable to log into the lxc session in from unity-greeter (same behaviour as before). But now there is no more popup if I want to report a bug. If I try 'sudo unity8-lxc-session' this happens: lxc-attach: attach.c: lxc_attach: 730 failed to get the init pid /usr/bin/unity8-lxc-session: 30: /usr/bin/unity8-lxc-session: cannot create /proc//root/etc/passwd: Directory nonexistent -- 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/1567037 Title: lxc-attach crashed with SIGSEGV in get_pty_on_host() Status in lxc package in Ubuntu: Fix Committed Bug description: Installed unity8-lxc, ran unity8-setup, then rebooted. Login to unity8 lxc session failed (somehow nothing happened), then I logged into Unity7 and the crash happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: lxc1 2.0.0~rc15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 6 20:11:34 2016 ExecutablePath: /usr/bin/lxc-attach InstallationDate: Installed on 2015-12-03 (124 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151203) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed root=UUID=dccfbc3c-48bc-43ed-9881-36efaa2ef6c5 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x563ee5318994 : movl $0x1,0x1c(%r14) PC (0x563ee5318994) ok source "$0x1" ok destination "0x1c(%r14)" (0x001c) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: lxc Stacktrace: #0 0x563ee5318994 in main () No symbol table info available. StacktraceTop: main () ThreadStacktrace: . Thread 1 (Thread 0x7fe20540f840 (LWP 2993)): #0 0x563ee5318994 in main () No symbol table info available. Title: lxc-attach crashed with SIGSEGV in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1567037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1521288] Re: Having a TV connected via SlimPort/HDMI does not route sound to it
Same for me, on Nexus 4, with latest OTA 10. -- 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/1521288 Title: Having a TV connected via SlimPort/HDMI does not route sound to it Status in Canonical Pocket Desktop: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: While a TV is connected to the phone via SlimPort/HDMI, audio should be routed to the TV. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1521288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561698] Re: Build hangs on s390x
Looks like that test fails on systemd machines if libpam-systemd isn't installed in the base system. buildds have been mangled to include minimal^ and standard^ and glib2.0 now builds. ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1561698 Title: Build hangs on s390x Status in glib2.0 package in Ubuntu: Fix Released Bug description: The build reproducibly hangs on the buildds on s390x. It's always at the same place, in the "642026" test. https://git.gnome.org/browse/glib/tree/glib/tests/642026.c I don't think it's this testsuite that is at fault though - the same thing builds on other Ubuntu architectures and for Debian s390x. The last successful build was 2.47.6-1 which used "Kernel version: Linux z13-019 4.3.0-6-generic #17-Ubuntu SMP Mon Jan 11 21:29:24 UTC 2016 s390x" and the latest failure was 2.47.92-1 "Kernel version: Linux z13-012 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:07:12 UTC 2016 s390x". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1561698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564965] Re: s390x tests should be re-enabled
Tests are re-enabled as of 2.48.0-1ubuntu4 ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1564965 Title: s390x tests should be re-enabled Status in glib2.0 package in Ubuntu: Fix Released Bug description: glib2.0 (2.48.0-1ubuntu3) xenial; urgency=medium * Revert the last change, don't run the tests on s390x for a first build. -- Matthias Klose Thu, 31 Mar 2016 20:56:40 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1564965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369493] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
** Tags added: armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1369493 Title: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Status in sysvinit package in Ubuntu: Confirmed Bug description: Upgrading xorg on Utopic (booted with upstart), the install dialog-box have displayed this warning: Setting up x11-common (1:7.7+7ubuntu2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults * Setting up X socket directories...[ OK ] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: sysv-rc 2.88dsf-41ubuntu18 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 15 12:12:53 2014 PackageArchitecture: all SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1369493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307883] Re: ca-certificates-java misses runtime dependency on initscripts
Yes, same problem here with Ubuntu on Windows. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1307883 Title: ca-certificates-java misses runtime dependency on initscripts Status in ca-certificates-java package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Triaged Bug description: Jitsi build-depends on openjdk-7-jre but the package fails to install in pbuilder and thus I currently cannot build the package. Here is the output I get while I am logged in to the trusty chroot. # aptitude install default-jdk [...] E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ca-certificates-java (20130815ubuntu1) ... /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: command not found the keytool command requires a mounted proc fs (/proc). dpkg: error processing package ca-certificates-java (--configure): subprocess installed post-installation script returned error exit status 1 Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ... /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found the java command requires a mounted proc fs (/proc). dpkg: error processing package openjdk-7-jre-headless:i386 (--configure): subprocess installed post-installation script returned error exit status 1 Setting up default-jre-headless (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jre:i386: openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre-headless:i386 is not configured yet. dpkg: error processing package openjdk-7-jre:i386 (--configure): dependency problems - leaving unconfigured Setting up default-jre (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386: openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre:i386 is not configured yet. dpkg: error processing package openjdk-7-jdk:i386 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of default-jdk: default-jdk depends on openjdk-7-jdk (>= 7~u3-2.1.1); however: Package openjdk-7-jdk:i386 is not configured yet. dpkg: error processing package default-jdk (--configure): dependency problems - leaving unconfigured Processing triggers for ca-certificates (20130906ubuntu2) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d /etc/ca-certificates/update.d/jks-keystore: 33: /etc/ca-certificates/update.d/jks-keystore: mountpoint: not found the keytool command requires a mounted proc fs (/proc). E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. Errors were encountered while processing: ca-certificates-java openjdk-7-jre-headless:i386 openjdk-7-jre:i386 openjdk-7-jdk:i386 default-jdk # mount /proc on /proc type proc (rw,relatime) tmpfs on /run/shm type tmpfs (rw,relatime) /dev/pts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1307883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13
Thanks John have made the change: #/sbin/dhclient { /sbin/dhclient flags=(attach_disconnected) { and rebooted: the error is gone now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1568485 Title: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 Status in apparmor package in Ubuntu: New Bug description: Get this logged on a fully upgraded 64 desktop (proposed archive enabled) kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log" pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 10 12:23:56 2016 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1568485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13
It needs to be set in the profile file /etc/apparmor.d/sbin.dhclient apply the following change --- a/sbin.dhclient 2016-02-25 06:32:17.0 -0800 +++ b/sbin.dhclient 2016-04-10 12:41:41.826906424 -0700 @@ -3,7 +3,7 @@ # Author: Jamie Strandboge #include -/sbin/dhclient { +/sbin/dhclient flags=(attach_disconnected) { #include #include #include -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1568485 Title: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 Status in apparmor package in Ubuntu: New Bug description: Get this logged on a fully upgraded 64 desktop (proposed archive enabled) kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log" pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 10 12:23:56 2016 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1568485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567377] Re: Select text popup not localized
On my device, the following command has an empty output: phablet@ubuntu-phablet:/usr/share$ find . -name ubuntu-ui-toolkit.mo so it looks like the UITK isn’t installing its translations any longer, that would be a recent regression. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1567377 Title: Select text popup not localized Status in Canonical System Image: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: Test case. - Switch the phone to Spanish. - Open webbrowser-app. - Go to slashdot.org - Select a text. Expected result. - The select text dialog is translated to Spanish. Actual result. - Dialog is in English. current build number: 301 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568583] Re: jackd crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1548103 *** https://bugs.launchpad.net/bugs/1548103 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1548103, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1568583/+attachment/4631815/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1568583/+attachment/4631817/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1568583/+attachment/4631820/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1568583/+attachment/4631821/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1568583/+attachment/4631822/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1568583/+attachment/4631823/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1568583/+attachment/4631824/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1548103 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1568583 Title: jackd crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in jackd2 package in Ubuntu: New Bug description: Started Rosegarden while listening to Spotify ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Apr 10 20:54:40 2016 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323) ProcCmdline: /usr/bin/jackd -T -ndefault -T -d alsa Signal: 6 SourcePackage: jackd2 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libjackserver.so.0 Title: jackd crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1568583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568273] Re: button appearance is broken
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1568273 Title: button appearance is broken Status in gtk+3.0 package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: GTK buttons have too many visual glitches, it looks like all default themes (Radiance, Ambiance and High Contrast) are not compatible with GTK 3.18 - open Nautilus, on left toolbar click on "Documents", click on "Home" = "Home" button on top bar looks wrong (1-bad.png) - point mouse over "Home" button on top bar = "Home" button looks OK (2-ok.png) - keep Nautilus open and dont touch it, open System Settings and go back to Nautilus = "Home" button on top bar suddenly looks OK (2-ok.png) - click on "Recent" on left toolbar = right side of "Recent" button doesnt have rounded corners (3-bad.png) - point mouse over "Recent" button on top bar = button will look fine until you move mouse pointer away this is just example but there are much more visual issues that happen randomly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: light-themes 14.04+16.04.20160324.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 9 13:23:43 2016 InstallationDate: Installed on 2016-04-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160407) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1568273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568576] [NEW] Thinkpad T460 & Ultra Dock - No audio output on dock plug
Public bug reported: Thinkpad T460, Ultra dock, 2 channel speakers connected to dock. 4.4.0-18 Kernel / 16.04. When the laptop is docked & speakers are connected to the dock audio connector, I get no audio outpout from the dock audio connector. Looks like the same issue as reported in: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680 However the pin quirks appear to be different for the T*60 series of laptops. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1568576 Title: Thinkpad T460 & Ultra Dock - No audio output on dock plug Status in alsa-driver package in Ubuntu: New Bug description: Thinkpad T460, Ultra dock, 2 channel speakers connected to dock. 4.4.0-18 Kernel / 16.04. When the laptop is docked & speakers are connected to the dock audio connector, I get no audio outpout from the dock audio connector. Looks like the same issue as reported in: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680 However the pin quirks appear to be different for the T*60 series of laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
I tried the nm packages in the proposed repositories and I'm experiencing crashes in nm-pptp-ppp-plugin: Apr 10 13:33:46 xps-9343 NetworkManager[778]: [1460309626.6913] audit: op="connection-activate" uuid="0c424828-8229-4ceb-acfd-237b46648424" name="VPNtest" pid=1869 uid=1000 result="success" Apr 10 13:33:46 xps-9343 NetworkManager[778]: [1460309626.6947] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: Started the VPN service, PID 21714 Apr 10 13:33:46 xps-9343 NetworkManager[778]: [1460309626.7058] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: Saw the service appear; activating connection Apr 10 13:33:46 xps-9343 NetworkManager[778]: [1460309626.7104] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: init (1) Apr 10 13:33:46 xps-9343 NetworkManager[778]: [1460309626.8098] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN connection: (ConnectInteractive) reply received Apr 10 13:33:47 xps-9343 NetworkManager[778]: ** Message: pppd started with pid 21723 Apr 10 13:33:47 xps-9343 NetworkManager[778]: [1460309627.7636] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: starting (3) Apr 10 13:33:47 xps-9343 pppd[21723]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Apr 10 13:33:47 xps-9343 NetworkManager[778]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Apr 10 13:33:47 xps-9343 NetworkManager[778]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Apr 10 13:33:47 xps-9343 NetworkManager[778]: (process:21723): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'g_variant_is_object_path (object_path)' failed Apr 10 13:33:47 xps-9343 kernel: [72071.405574] pppd[21723]: segfault at 8 ip 7fd0b43feb0c sp 7ffe051b47f0 error 4 in nm-pptp-pppd-plugin.so[7fd0b43fd000+3000] Apr 10 13:33:47 xps-9343 NetworkManager[778]: ** (nm-pptp-service:21714): WARNING **: pppd died with signal 11 Apr 10 13:33:47 xps-9343 NetworkManager[778]: [1460309627.8919] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: failed: connect-failed (1) Apr 10 13:33:47 xps-9343 NetworkManager[778]: [1460309627.8921] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: stopping (5) Apr 10 13:33:47 xps-9343 NetworkManager[778]: [1460309627.8922] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: stopped (6) Apr 10 13:33:47 xps-9343 NetworkManager[778]: [1460309627.8930] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state change reason: unknown (0) Apr 10 13:33:47 xps-9343 NetworkManager[778]: [1460309627.8943] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN service disappeared -- 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/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Triaged Status in network-manager-applet package in Ubuntu: Triaged Status in network-manager-iodine package in Ubuntu: Triaged Status in network-manager-openconnect package in Ubuntu: Triaged Status in network-manager-openvpn package in Ubuntu: Triaged Status in network-manager-pptp package in Ubuntu: Triaged Status in network-manager-vpnc package in Ubuntu: Triaged Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by
[Touch-packages] [Bug 1568570] Re: ntpd crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1548325 *** https://bugs.launchpad.net/bugs/1548325 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1548325, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1568570/+attachment/4631713/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1568570/+attachment/4631715/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1568570/+attachment/4631719/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1568570/+attachment/4631720/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1568570/+attachment/4631721/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1568570/+attachment/4631722/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1568570/+attachment/4631723/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1548325 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1568570 Title: ntpd crashed with SIGABRT in raise() Status in ntp package in Ubuntu: New Bug description: Occurs on bootup, after login. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Apr 10 11:52:31 2016 ExecutablePath: /usr/sbin/ntpd InstallationDate: Installed on 2016-03-08 (33 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=afe68198-4970-4b3a-85f0-aa864218414d ro quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: ntp StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () Title: ntpd crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1568570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556134] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()
*** This bug is a duplicate of bug 1553358 *** https://bugs.launchpad.net/bugs/1553358 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libopenobex (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libopenobex in Ubuntu. https://bugs.launchpad.net/bugs/1556134 Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal() Status in libopenobex package in Ubuntu: Confirmed Bug description: on launch this crash occurs ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libopenobex2 1.7.1-4 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Mar 9 16:14:37 2016 Dependencies: gcc-6-base 6-20160227-0ubuntu1 libc6 2.21-0ubuntu6 libgcc1 1:6-20160227-0ubuntu1 libudev1 229-2ubuntu1 libusb-1.0-0 2:1.0.20-1 ExecutablePath: /usr/sbin/obex-check-device InstallationDate: Installed on 2016-02-11 (28 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: /usr/sbin/obex-check-device 01da ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f8783a75674 <__GI_strtoul_l_internal+68>: movsbq (%r14),%rax PC (0x7f8783a75674) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libopenobex StacktraceTop: __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f8783dff500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297 main () Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: Upgraded to xenial on 2016-03-02 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1556134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556134] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()
*** This bug is a duplicate of bug 1553358 *** https://bugs.launchpad.net/bugs/1553358 what's the point of having private bugs? is it so that I cannot leave a comment or check it out? filing public bugs as duplicates of private bugs doesn't seem very helpful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libopenobex in Ubuntu. https://bugs.launchpad.net/bugs/1556134 Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal() Status in libopenobex package in Ubuntu: Confirmed Bug description: on launch this crash occurs ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libopenobex2 1.7.1-4 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Mar 9 16:14:37 2016 Dependencies: gcc-6-base 6-20160227-0ubuntu1 libc6 2.21-0ubuntu6 libgcc1 1:6-20160227-0ubuntu1 libudev1 229-2ubuntu1 libusb-1.0-0 2:1.0.20-1 ExecutablePath: /usr/sbin/obex-check-device InstallationDate: Installed on 2016-02-11 (28 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: /usr/sbin/obex-check-device 01da ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f8783a75674 <__GI_strtoul_l_internal+68>: movsbq (%r14),%rax PC (0x7f8783a75674) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libopenobex StacktraceTop: __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f8783dff500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297 main () Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: Upgraded to xenial on 2016-03-02 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1556134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail
This broke the rendering of Input font for me. ** Attachment added: "left: patched, right: non-patched" https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1547196/+attachment/4631652/+files/2016-04-10_19-00-06.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1547196 Title: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail Status in freetype package in Ubuntu: Confirmed Status in freetype package in Debian: New Bug description: This is mostly a tracking bug for this discussion on ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu- devel/2016-February/039224.html The following precise-era patch was recently removed from freetype: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/freetype/wily/view/head:/debian/patches- freetype/revert_scalable_fonts_metric.patch which caused a number of visual effects in various applications. In Emacs, the lines get vertically closer so that more lines are visible on screen. This is subtle and doesn't look too bad otherwise. However, in Claws-Mail several negative effects were noticed. The lines in the Summary window are more squished together and the characters appear squished too. This is with Sans 10 font. This is less readable. In the Message window it's worse. There I use Ubuntu Mono 14. The problem isn't the vertical spacing, but the horizontal spacing. Now there is more space between characters and that actually makes the window less readable. I will contact the upstream Claws mailing list to see if they have any thoughts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libfreetype6 2.6.1-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 18 14:34:57 2016 Dependencies: gcc-6-base 6-20160217-0ubuntu1 libc6 2.21-0ubuntu6 libgcc1 1:6-20160217-0ubuntu1 libpng12-0 1.2.54-1ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-22 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: freetype UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1547196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13
Thanks Christian, but i wonder where to set that setting. Is it into: /sys/kernel/security/apparmor/profiles or somewhere else ? In fact it seems that there is no kernel's 'profile' set at all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1568485 Title: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 Status in apparmor package in Ubuntu: New Bug description: Get this logged on a fully upgraded 64 desktop (proposed archive enabled) kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log" pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 10 12:23:56 2016 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1568485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406810] Re: screen is garbled with 14.10 (was fine with 14.04)
Nicolas Jungers, you would want to keep testing the latest daily build of Xenial via http://cdimage.ubuntu.com/daily-live/current/ given fixes are landing there on a daily basis. Could you please advise? -- 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/1406810 Title: screen is garbled with 14.10 (was fine with 14.04) Status in xorg package in Ubuntu: Incomplete Bug description: On a iMac Alu 2010, when upgrading from 14.04 desktop to 14.10 desktop or installing 10.10 server (SSH package only) the screen shows thin horizontal lines moving on a black background. /etc/X11/xorg.conf is absent (using default config), /var/log/Xorg.0.log doesn't show any error beside the lack of the fglrx module. But I doubt it's relevant with the symptoms appearing on the server install. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] [1002:944a] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b5] InstallationDate: Installed on 2015-01-01 (440 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Apple Inc. iMac11,1 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-79-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/17/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM111.88Z.0034.B02.1003171314 dmi.board.name: Mac-F2268DAE dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DAE dmi.modalias: dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE: dmi.product.name: iMac11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 16 19:43:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314871] Re: Graphics freeze, with applications continuing working properly
Justas Azna, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- 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/1314871 Title: Graphics freeze, with applications continuing working properly Status in xorg package in Ubuntu: Incomplete Bug description: Happens at random during normal desktop usage. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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: Thu May 1 09:21:51 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] InstallationDate: Installed on 2014-04-27 (3 days ago) InstallationMedia: Ubuntu-Kylin 14.04 LTS "Trusty Tahr" - Release amd64 (20140417.1) MachineType: Dell Inc. Vostro 3400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RXV7H dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3400 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: freetype (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1547196 Title: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail Status in freetype package in Ubuntu: Confirmed Status in freetype package in Debian: New Bug description: This is mostly a tracking bug for this discussion on ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu- devel/2016-February/039224.html The following precise-era patch was recently removed from freetype: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/freetype/wily/view/head:/debian/patches- freetype/revert_scalable_fonts_metric.patch which caused a number of visual effects in various applications. In Emacs, the lines get vertically closer so that more lines are visible on screen. This is subtle and doesn't look too bad otherwise. However, in Claws-Mail several negative effects were noticed. The lines in the Summary window are more squished together and the characters appear squished too. This is with Sans 10 font. This is less readable. In the Message window it's worse. There I use Ubuntu Mono 14. The problem isn't the vertical spacing, but the horizontal spacing. Now there is more space between characters and that actually makes the window less readable. I will contact the upstream Claws mailing list to see if they have any thoughts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libfreetype6 2.6.1-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 18 14:34:57 2016 Dependencies: gcc-6-base 6-20160217-0ubuntu1 libc6 2.21-0ubuntu6 libgcc1 1:6-20160217-0ubuntu1 libpng12-0 1.2.54-1ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-22 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: freetype UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1547196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568544] Re: Scopes are smoothest with no microSD card
Some more info: the card is a class 4 card which according to articles like this one http://pocketnow.com/android/does-using-a-faster-sdcard- make-your-phone-faster can slow down a phones performance. So perhaps it's just the nature of the hardware, but I'd rather have the bug rejected than not mention it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1568544 Title: Scopes are smoothest with no microSD card Status in unity-scopes-shell package in Ubuntu: New Bug description: I removed my microSD card for the first time on the day the OTA-10 update arrived. After the update, the scopes were smooth as silk and I thought this was as a result of the OTA. But after re-inserting the microSD card they are back to their normal way; smooth for a few minutes, jerky for a few minutes. Card: SanDisk 16GB Micro SD HC Scopes: Today, Apps, My Videos, Dictionary, Simon's Cat, Discerning Duck, Crafting, Command Line This is 100% reproducable on every ocassion now when I remove or insert the card and either symptom remains - ie, it's not something that just lasts a moment and then corrects itself. I have the Log Viewer app installed. I can upload any logs requested. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1568544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568544] [NEW] Scopes are smoothest with no microSD card
Public bug reported: I removed my microSD card for the first time on the day the OTA-10 update arrived. After the update, the scopes were smooth as silk and I thought this was as a result of the OTA. But after re-inserting the microSD card they are back to their normal way; smooth for a few minutes, jerky for a few minutes. Card: SanDisk 16GB Micro SD HC Scopes: Today, Apps, My Videos, Dictionary, Simon's Cat, Discerning Duck, Crafting, Command Line This is 100% reproducable on every ocassion now when I remove or insert the card and either symptom remains - ie, it's not something that just lasts a moment and then corrects itself. I have the Log Viewer app installed. I can upload any logs requested. Thanks! ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1568544 Title: Scopes are smoothest with no microSD card Status in unity-scopes-shell package in Ubuntu: New Bug description: I removed my microSD card for the first time on the day the OTA-10 update arrived. After the update, the scopes were smooth as silk and I thought this was as a result of the OTA. But after re-inserting the microSD card they are back to their normal way; smooth for a few minutes, jerky for a few minutes. Card: SanDisk 16GB Micro SD HC Scopes: Today, Apps, My Videos, Dictionary, Simon's Cat, Discerning Duck, Crafting, Command Line This is 100% reproducable on every ocassion now when I remove or insert the card and either symptom remains - ie, it's not something that just lasts a moment and then corrects itself. I have the Log Viewer app installed. I can upload any logs requested. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1568544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568539] [NEW] [Unity 7] Displays: Only 1 external workspace setting mssing
Public bug reported: If a user is using multiple virtual workspaces, and is connected to external display at the same time, all the workspaces are visible on the external display too. A setting of "Only one available workspace on external display" is missing! (Unfortunately, the setting of "Always on a visible workspace" will not cut it, when on a management meeting and need opening more that one window on external display!) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1568539 Title: [Unity 7] Displays: Only 1 external workspace setting mssing Status in bluez package in Ubuntu: New Bug description: If a user is using multiple virtual workspaces, and is connected to external display at the same time, all the workspaces are visible on the external display too. A setting of "Only one available workspace on external display" is missing! (Unfortunately, the setting of "Always on a visible workspace" will not cut it, when on a management meeting and need opening more that one window on external display!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1568539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568474] Re: systemd-udevd[473]: Process '/lib/udev/hdparm' failed with exit code 5.
Please add some debugging output to /lib/udev/hdparm with sudo sed -i '2 s_^_set -x; exec 2>/tmp/hdparm.txt_' /lib/udev/hdparm then re-run the event with sudo udevadm trigger --action=add /sys/block/sda --verbose then attach /tmp/hdparm.txt here. Thanks! ** Package changed: systemd (Ubuntu) => hdparm (Ubuntu) ** Changed in: hdparm (Ubuntu) Status: New => Incomplete ** Summary changed: - systemd-udevd[473]: Process '/lib/udev/hdparm' failed with exit code 5. + Process '/lib/udev/hdparm' failed with exit code 5 -- 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/1568474 Title: Process '/lib/udev/hdparm' failed with exit code 5 Status in hdparm package in Ubuntu: Incomplete Bug description: get that error logged on a fully upgraded (proposed archive enabled) xenial 64 bits system (hdparm 9.48+ds-1) Searching about systemd-udevd.service, it is found into /lib/systemd/ but there is a problem: oem@u64:~$ ls -l systemd-udevd.service ls: cannot access 'systemd-udevd.service': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 10 11:41:07 2016 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1568474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446053] Re: Font corruption some characters suddenly not rendered after login or after a period of usage
The laptop is now on 15.10 and I have not seen the bug. It may have been fixed in 15.04, I can't remember it was so long ago since I did that upgrade. -- 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/1446053 Title: Font corruption some characters suddenly not rendered after login or after a period of usage Status in xorg package in Ubuntu: Incomplete Bug description: This has occurred multiple times on my machine (Dell Inspiron 13 7000 series laptop), it happens without warning. After which time suddenly application windows will fail to render certain characters making everything unreadable. In the past it has happened immediately after login, this time it happened after ~30 minutes usage from a cold boot. See attached screenshot. This doesn't happen for every window, chrome is generally ok, as are the unity launcher. The tools in the system tray and the power off menu are affected, as are nautilus, gedit, and application menus generally. Rolling over labels sometimes causes them to rener properly while the mouse is over them. Terminal is fine There is a workaround which is to change the font antialiasing settings with unity tweak tool, however this isn't a permanent fix - last time it was set to RGBA, so I changed it to Grayscale. This time it happened it was set to Grayscale and I set it to RGBA and it fixes it. I don't know enough to know whether this is a video driver issue, or a problem with gtk or what, so it's possible you may need to recategorise this defect. One other thing that may be useful info is that twiddling the antialiasing drop-down fixes and breaks the font rendering on the fly, when I see this problem. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 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: Mon Apr 20 06:39:41 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0675] InstallationDate: Installed on 2015-04-05 (14 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7348 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=/dev/mapper/LVM_VG1-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 08FH29 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/26/2014:svnDellInc.:pnInspiron7348:pvrA01:rvnDellInc.:rn08FH29:rvrA00:cvnDellInc.:ct10:cvrA01: dmi.product.name: Inspiron 7348 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 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.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Apr 20 05:54:03 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19528 vendor SDC xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1446053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 115536] Re: apt-cdrom add fails to mount the medium
Hello, If I type ihis command i a terminal sudo apt-cdrom -m add I get this result apt-cdrom -m add Using CD-ROM mount point /media/cdrom/ Identifying... E: Unable to change to /media/cdrom/ - chdir (2: No such file or directory) E: No CD-ROM could be auto-detected or found using the default mount point. You may try the --cdrom option to set the CD-ROM mount point. See 'man apt-cdrom' for more information about the CD-ROM auto-detection and mount point. It seem the cdrom mount point it in the seme folder that the other mount point device In my case is this /media/mparchet/Ubuntu\ 15.10\ amd64/ Sould I create a symbolik link /media/cdrom/that point on the cdrom sudo ln -s /media/mparchet/Ubuntu\ 15.10\ amd64/ /media/cdrom I tesed this semm work. Coul you confirm thos Thanks for your help mparchet -- 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/115536 Title: apt-cdrom add fails to mount the medium Status in apt package in Ubuntu: Invalid Status in synaptic package in Ubuntu: Invalid Bug description: Binary package hint: apt While running 'apt-cdrom add' in my notebook its always fails saying: E: Failed to mount the cdrom. APT looks into /etc/fstab to get the default cdrom mount point. My fstab looks like: /dev/cdrom/cdrom udf,iso9660 user,noauto 0 0 APT tries to mount '/cdrom/' instead of just '/cdrom' (withou slash). If I change fstab and add the slash in the mount point everything works well. Suggestion: a) APT needs to use the hal mounting point instead the /etc/fstab, so it would works with no mention in fstab b) The default fstab mounting point should be '/cdrom/' instead of just '/cdrom' c) The default mounting point where apt looks into should be '/cdrom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/115536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
will this bug fixed before formal release of Ubuntu 16.04 LTS? For nautilus 3.18.4.is.3.14.3: --- nautilus-3.18.4.is.3.14.3.orig/src/nautilus-window.c +++ nautilus-3.18.4.is.3.14.3/src/nautilus-window.c @@ -1554,7 +1554,24 @@ nautilus_window_constructed (GObject *se window->details->toolbar = create_toolbar (window); desktop = g_getenv ("XDG_CURRENT_DESKTOP"); - if (desktop && strstr (desktop, "GNOME")) + + gchar **desktop_names; + gboolean is_gnome; + int i; + + is_gnome = FALSE; + if (desktop != NULL) { + desktop_names = g_strsplit (desktop, ":", 0); + for (i = 0; desktop_names[i]; ++i) { + if (!g_strcmp0 (desktop_names[i], "GNOME")) { + is_gnome = TRUE; + break; + } + } + g_strfreev (desktop_names); + } + + if (is_gnome) gtk_window_set_titlebar (GTK_WINDOW (window), window->details->toolbar); else { gtk_container_add (GTK_CONTAINER (grid), window->details->toolbar); Hope to get nautilus fixed soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Triaged Status in pyxdg package in Ubuntu: Confirmed Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568528] [NEW] ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789")
Public bug reported: Ubuntu 15.10 4.2.0-35 network-manager Ubuntu sources: network-manager_1.0.4.orig.tar.xz built with: dpkg-buildpackage -b -m"Jean-Christophe Manciot " ... = NetworkManager 1.0.4: src/platform/tests/test-suite.log = # TOTAL: 29 # PASS: 27 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 2 .. contents:: :depth: 2 ERROR: test-link-linux == # random seed: R02S51e6130ccfacff746e76534eba2e4658 1..7 # Start of link tests ok 1 /link/bogus PASS: test-link-linux 1 /link/bogus ok 2 /link/loopback PASS: test-link-linux 2 /link/loopback ok 3 /link/internal PASS: test-link-linux 3 /link/internal ok 4 /link/external PASS: test-link-linux 4 /link/external ** NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789") # Start of software tests Aborted (core dumped) # NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789") ERROR: test-link-linux - too few tests run (expected 7, got 4) ERROR: test-link-linux - exited with status 134 (terminated by signal 6?) Full log attached. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Full log" https://bugs.launchpad.net/bugs/1568528/+attachment/4631500/+files/Error%20building%201.0.4.log -- 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/1568528 Title: ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789") Status in network-manager package in Ubuntu: New Bug description: Ubuntu 15.10 4.2.0-35 network-manager Ubuntu sources: network-manager_1.0.4.orig.tar.xz built with: dpkg-buildpackage -b -m"Jean-Christophe Manciot " ... = NetworkManager 1.0.4: src/platform/tests/test-suite.log = # TOTAL: 29 # PASS: 27 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 2 .. contents:: :depth: 2 ERROR: test-link-linux == # random seed: R02S51e6130ccfacff746e76534eba2e4658 1..7 # Start of link tests ok 1 /link/bogus PASS: test-link-linux 1 /link/bogus ok 2 /link/loopback PASS: test-link-linux 2 /link/loopback ok 3 /link/internal PASS: test-link-linux 3 /link/internal ok 4 /link/external PASS: test-link-linux 4 /link/external ** NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789") # Start of software tests Aborted (core dumped) # NetworkManager:ERROR:test-link.c:303:test_software: assertion failed (value == "789"): ("788" == "789") ERROR: test-link-linux - too few tests run (expected 7, got 4) ERROR: test-link-linux - exited with status 134 (terminated by signal 6?) Full log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1568528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531442] Re: reboot switches to us keyboard layout on console
@Michał: Almost surely a different cause, unless you upgraded and something went wrong and you have an old keyboard-configuration package. Please copy&paste the output of systemctl status console-setup -- 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/1531442 Title: reboot switches to us keyboard layout on console Status in console-setup package in Ubuntu: Fix Released Bug description: On 16.04 server without X after each reboot my keyboard is set to us layout, althouth configured to german. After logging in to a console and 'sudo setup' the german layout is selected. The same with 'sudo dpkg-reconfigure keyboard-configuration'. The machine is running under Virtual-Box 5.0.12 on Windows if this should be of interest. ProblemType: Bug ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 ConsoleSetup: # CONFIGURATION FILE FOR SETUPCON # Consult the console-setup(5) manual page. ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Lat15" FONTFACE="VGA" FONTSIZE="8x16" VIDEOMODE= # The following is an example how to use a braille font # FONT='lat9w-08.psf.gz brl-8x8.psf' Date: Wed Jan 6 10:28:45 2016 Dependencies: adduser 3.113+nmu3ubuntu4 apt 1.1.10 apt-utils 1.1.10 coreutils 8.23-4ubuntu2 debconf 1.5.58ubuntu1 debconf-i18n 1.5.58ubuntu1 debianutils 4.5.1 dpkg 1.18.3ubuntu1 e2fslibs 1.42.13-1ubuntu1 e2fsprogs 1.42.13-1ubuntu1 gcc-5-base 5.3.1-5ubuntu1 gnupg 1.4.19-6ubuntu1 gpgv 1.4.19-6ubuntu1 init-system-helpers 1.24ubuntu2 initscripts 2.88dsf-59.2ubuntu3 insserv 1.14.0-5ubuntu3 libacl1 2.2.52-2 libapt-inst2.0 1.1.10 libapt-pkg5.0 1.1.10 libattr1 1:2.4.47-2 libaudit-common 1:2.4.4-4ubuntu1 libaudit1 1:2.4.4-4ubuntu1 libblkid1 2.27.1-1ubuntu3 libbz2-1.0 1.0.6-8 libc6 2.21-0ubuntu5 libcomerr2 1.42.13-1ubuntu1 libdb5.3 5.3.28-11 libfdisk1 2.27.1-1ubuntu3 libgcc1 1:5.3.1-5ubuntu1 libgcrypt20 1.6.4-4 libgpg-error0 1.21-1 libgpm2 1.20.4-6.1 liblocale-gettext-perl 1.07-1 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.27.1-1ubuntu3 libncursesw5 6.0+20151024-2ubuntu1 libpam-modules 1.1.8-3.1ubuntu3 libpam-modules-bin 1.1.8-3.1ubuntu3 libpam0g 1.1.8-3.1ubuntu3 libpcre3 2:8.35-7.1ubuntu1 libreadline6 6.3-8ubuntu1 libselinux1 2.4-3 libsemanage-common 2.3-1build2 libsemanage1 2.3-1build2 libsepol1 2.4-2 libsmartcols1 2.27.1-1ubuntu3 libss2 1.42.13-1ubuntu1 libstdc++6 5.3.1-5ubuntu1 libsystemd0 228-3ubuntu1 libtext-charwidth-perl 0.04-7build4 libtext-iconv-perl 1.7-5build3 libtext-wrapi18n-perl 0.06-7.1 libtinfo5 6.0+20151024-2ubuntu1 libudev1 228-3ubuntu1 libusb-0.1-4 2:0.1.12-27 libustr-1.0-1 1.0.4-5 libuuid1 2.27.1-1ubuntu3 lsb-base 9.20150917ubuntu1 mount 2.27.1-1ubuntu3 multiarch-support 2.21-0ubuntu5 passwd 1:4.1.5.1-1.1ubuntu7 perl-base 5.20.2-6 psmisc 22.21-2.1 readline-common 6.3-8ubuntu1 sensible-utils 0.0.9 sysv-rc 2.88dsf-59.2ubuntu3 sysvinit-utils 2.88dsf-59.2ubuntu3 tar 1.28-2.1 tzdata 2015g-1 ubuntu-keyring 2012.05.19 util-linux 2.27.1-1ubuntu3 uuid-runtime 2.27.1-1ubuntu3 zlib1g 1:1.2.8.dfsg-2ubuntu4 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-12-23 (14 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151115) JournalErrors: -- Logs begin at Wed 2016-01-06 10:25:57 CET, end at Wed 2016-01-06 10:27:14 CET. -- Jan 06 10:25:58 hostname kernel: ACPI: RSDP 0x000E 24 (v02 VBOX ) Jan 06 10:25:58 hostname kernel: ACPI: XSDT 0x7FFF0030 3C (v01 VBOX VBOXXSDT 0001 ASL 0061) Jan 06 10:25:58 hostname kernel: ACPI: FACP 0x7FFF00F0 F4 (v04 VBOX VBOXFACP 0001 ASL 0061) Jan 06 10:25:58 hostname kernel: ACPI: DSDT 0x7FFF0470 001CEB (v01 VBOX VBOXBIOS 0002 INTL 20100528) Jan 06 10:25:58 hostname kernel: ACPI: FACS 0x7FFF0200 40 Jan 06 10:25:58 hostname kernel: ACPI: FACS 0x7FFF0200 40 Jan 06 10:25:58 hostname kernel: ACPI: APIC 0x7FFF0240 5C (v02 VBOX VBOXAPIC 0001 ASL 0061) Jan 06 10:25:58 hostname kernel: ACPI: SSDT 0x7FFF02A0 0001CC (v01 VBOX VBOXCPUT 0002 INTL 20100528) Jan 06 10:25:58 hostname kernel: ACPI: 2 ACPI AML tables successfully acquired and loaded Jan 06 10:25:58 hostname kernel: PCCT header not found. Jan 06 10:25:58 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code Jan 06 10:25:58 hostname kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150818/hwxface-580) Jan 06 10:25:58 hostname kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150818/hwxfa
[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1551858 Title: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Connecting to the latest generation Apple BT keyboard ( the one with the USB port & no batteries ) fails on an Ubuntu Touch device, as when you press the "Connect" button on the device page, a dialog titled "Bluetooth Pairing Request" is displayed, with the following text: Please confirm that the PIN displayed on 'Magic Keyboard' matches this one: XX The dialog has "Cancel" and "Confirm PIN" buttons. The keyboard has no display on which a PIN could be displayed. When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X, ... ) to connect this keyboard all that's necessary is to click/press the 'Connect' button in the appropriate place, and the keyboard automatically connects, and is usable with no other actions required from the user. Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez 5.36-0ubuntu2~overlay1 installed. Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37 installed from silo 39. Note, after dismissing the dialog, subsequent attempts to connect may not re-display the PIN dialog, instead nothing happens. I've found that this requires power cycling the keyboard to clear and cause the PIN dialog to be displayed again. [bluetooth]# show Controller B8:64:91:48:2B:1E Name: Aquaris E4.5 Ubuntu Edition Alias: Aquaris E4.5 Ubuntu Edition Class: 0x1c020c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0525 Discovering: no [bluetooth]# devices Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3 Device DE:76:E2:04:9D:6F BB-9D6F Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03 Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8 Device 84:38:35:67:0C:3D ubuntu-0 Device 04:69:F8:C2:A0:09 tony espy’s Keyboard Device 00:21:3C:A0:14:A6 Jawbone ERA Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7 Device info *before* pairing attempt: Device 04:69:F8:C2:A0:09 Name: tony espy’s Keyboard Alias: tony espy’s Keyboard Class: 0x002540 Icon: input-keyboard Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no Modalias: bluetooth:v004Cp0267d0066 No changes in any of the attributes after *after* the pairing attempt ( output of info command is the same ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed -- 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/1551858 Title: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Connecting to the latest generation Apple BT keyboard ( the one with the USB port & no batteries ) fails on an Ubuntu Touch device, as when you press the "Connect" button on the device page, a dialog titled "Bluetooth Pairing Request" is displayed, with the following text: Please confirm that the PIN displayed on 'Magic Keyboard' matches this one: XX The dialog has "Cancel" and "Confirm PIN" buttons. The keyboard has no display on which a PIN could be displayed. When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X, ... ) to connect this keyboard all that's necessary is to click/press the 'Connect' button in the appropriate place, and the keyboard automatically connects, and is usable with no other actions required from the user. Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez 5.36-0ubuntu2~overlay1 installed. Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37 installed from silo 39. Note, after dismissing the dialog, subsequent attempts to connect may not re-display the PIN dialog, instead nothing happens. I've found that this requires power cycling the keyboard to clear and cause the PIN dialog to be displayed again. [bluetooth]# show Controller B8:64:91:48:2B:1E Name: Aquaris E4.5 Ubuntu Edition Alias: Aquaris E4.5 Ubuntu Edition Class: 0x1c020c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0525 Discovering: no [bluetooth]# devices Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3 Device DE:76:E2:04:9D:6F BB-9D6F Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03 Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8 Device 84:38:35:67:0C:3D ubuntu-0 Device 04:69:F8:C2:A0:09 tony espy’s Keyboard Device 00:21:3C:A0:14:A6 Jawbone ERA Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7 Device info *before* pairing attempt: Device 04:69:F8:C2:A0:09 Name: tony espy’s Keyboard Alias: tony espy’s Keyboard Class: 0x002540 Icon: input-keyboard Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no Modalias: bluetooth:v004Cp0267d0066 No changes in any of the attributes after *after* the pairing attempt ( output of info command is the same ). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568520] Re: Expose pressedBackgroundColor in PageHeaderStyle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1568520 Title: Expose pressedBackgroundColor in PageHeaderStyle Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: At the moment, when you press on a header action button, it shows a "LightGrey" background. It seems the property setting this color is defined at http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/IconButtonStyle.qml#L36. This color works fine for white header backgrounds. But once you change the header background to blue, red or any other color, it looks odd. Please expose a property to change this color in the PageHeaderStyle. Something like pressedBackgroundColor would suffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1568520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568520] [NEW] Expose pressedBackgroundColor in PageHeaderStyle
Public bug reported: At the moment, when you press on a header action button, it shows a "LightGrey" background. It seems the property setting this color is defined at http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/IconButtonStyle.qml#L36. This color works fine for white header backgrounds. But once you change the header background to blue, red or any other color, it looks odd. Please expose a property to change this color in the PageHeaderStyle. Something like pressedBackgroundColor would suffice. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed ** Summary changed: - Expose pressedbackgroundcolor in PageHeaderStyle + Expose pressedBackgroundColor in PageHeaderStyle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1568520 Title: Expose pressedBackgroundColor in PageHeaderStyle Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: At the moment, when you press on a header action button, it shows a "LightGrey" background. It seems the property setting this color is defined at http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/IconButtonStyle.qml#L36. This color works fine for white header backgrounds. But once you change the header background to blue, red or any other color, it looks odd. Please expose a property to change this color in the PageHeaderStyle. Something like pressedBackgroundColor would suffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1568520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568286] Re: Gallery app freezes after upstart
Some additional information: Gallery app database is 64 KB Storage divided as follows: Used by Ubuntu: 2.4 GB Videos: 131 MB Audio: 136 MB Pictures: 432 MB Other files: 1.1 GB Used by applications: 584 MB Total free space: 2.4 GB -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1568286 Title: Gallery app freezes after upstart Status in gallery-app package in Ubuntu: New Bug description: Device: BQ Aquaris E4.5 OS version: rc-proposed r309 Storage: 2.4 GB free, pictures occupying 452 MB and videos 131 MB Steps: 1. Open the Gallery app 2. Wait for picture thumbnails to display 3. Latest dates are showing, but no thumbnails 4. App totally unresponsive for several minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1568286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568310] Re: BQ E4.5 (OTA-10): gallery-app tries to index thousands of files on the SD card, but should not
I don't know if this is related, but the gallery app on my BQ E4.5 also takes forever to load pictures. I have filed another bug about this here https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1568286. Some additional information: Gallery app database is 64 KB Storage divided as follows: Used by Ubuntu: 2.4 GB Videos: 131 MB Audio: 136 MB Pictures: 432 MB Other files: 1.1 GB Used by applications: 584 MB Total free space: 2.4 GB -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1568310 Title: BQ E4.5 (OTA-10): gallery-app tries to index thousands of files on the SD card, but should not Status in gallery-app package in Ubuntu: Confirmed Bug description: The app gallery did not started anymore in my BQ E4.5, it was just sitting there and loading for hours without coming to an end. I investigated it with strace and lsof and saw the app was searching through all the 100.000 files (OSM tiles) on my SD card. While the SD card managment app supports placing a file there with the name '.nomedia' so the SD Card app ignores all files and dirs below: $ ls -la /media/phablet/4BDC-71D9/Maps total 840900 drwxr-xr-x 3 phablet phablet 4096 Apr 7 09:25 . drwxr-xr-x 8 phablet phablet 4096 Jan 1 1970 .. -rw-r--r-- 1 phablet phablet 0 Apr 4 14:58 .nomedia drwxr-xr-x 19 phablet phablet 4096 Apr 4 14:08 osm $ find /media/phablet/4BDC-71D9/Maps/osm | wc -l 129236 it seems that the gallery-app does not honor this file '.nomedia'. Any idea for a workaround in the gallery-app? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1568310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp