[Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
Ok, reproduced with focal and broken seeds from an older image, symptoms are exactly the same (including ps/pstree output). The problem is caused by blocking on snapd.seeded.service (which waits for seeding to complete, but it's never going to complete with broken seeds). Given that this is an edge case (we don't expect images with broken seeds) and focal images have been fixed already, I'm lowering the priority. We will discuss what to do to handle this gracefully. ** Changed in: snapd Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
@Mark does 'snap changes' (and then 'snap change ' if you see any failed changes) reveal antyhing interesing? Some of the older focal images had broken seeds that would never succeed, potentially causing other issues. -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
Also, the list of installed snaps may be relevant in understanding what happens. -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
I'm tentatively adding systemd/dpkg. ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865519] Re: apparmor depends on python3
** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Wishlist -- 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/1865519 Title: apparmor depends on python3 Status in snapd: Triaged Status in apparmor package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: The TL;DR; - AppArmor depends on python3 to support aa-status. - snapd depends on apparmor. - buildd images have no python - building snaps requires snapd - snapd does not require aa-status - building snaps unnecessarily installs python3 onto the system Proposal: - Split runtime requirements from apparmor into apparmor-minimal - have apparmor depend on apparmor-minimal - change snapd's dependency on apparmor to apparmor-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1865519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps
The problem is still affecting current Cosmic image (from 11th of June) and has been reported on the https://forum.snapcraft.io/t/gnome- calculator-failed-to-create-symbolic-link/5742/22 ; any reason the re- order seed.yaml hasn't landed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Confirmed Status in snapd: New Status in ubuntu-meta package in Ubuntu: New Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
*** This bug is a duplicate of bug 1655936 *** https://bugs.launchpad.net/bugs/1655936 Marked this bug as duplicate of #1655936 to unconfuse errors.ubuntu.com (even though the bugs are technically different issues and the one from this bug was fixed long time ago). ** This bug has been marked a duplicate of bug 1655936 clients crash with "UbuntuClientIntegration: connection to Mir server failed." -- 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/1363946 Title: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale Status in Canonical System Image: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: unity8-dash gets into a respawn loop when the selected locale is unavailable. While it's understood that incorrect locale might result in unexpected behaviour, but aborting feels excessive. .log file mentions: ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for client, config file: : unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope c-17178aae: locale::facet::_S_create_c_locale name not ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140828.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Mon Sep 1 11:55:15 2014 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1409258182 InstallationDate: Installed on 2014-09-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140901-020204) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libstlport.so /android/system/lib/libgccdemangle.so /android/system/lib/libm.so /android/system/lib/libcorkscrew.so /android/system/lib/liblog.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/libc.so /android/system/lib/libcutils.so /android/system/lib/libGLESv2.so /android/system/lib/libEGL.so /android/system/lib/libdsyscalls.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 6 SourcePackage: unity8 StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so Title: unity8-dash crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1363946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
@Daniel I see your point about Mir. Anyway, all I'm saying is this problem manifested via https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb is completely different from the original problem described in this bug. The only common thing is qFatal() gets called. In the original problem it was called directly by unity8-dash in response to boost throwing exception on incorrect locale (which was fixed by the attached MP). In this new case this is something else in the stack calling qFatal and aborting unity8-dash and I see no evidence of locale being involved. To sum it up, I think it's a different bug and I don't think unity- scopes-shell (the dash) or unity-scopes-api are responsible for this. -- 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/1363946 Title: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale Status in Canonical System Image: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: unity8-dash gets into a respawn loop when the selected locale is unavailable. While it's understood that incorrect locale might result in unexpected behaviour, but aborting feels excessive. .log file mentions: ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for client, config file: : unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope c-17178aae: locale::facet::_S_create_c_locale name not ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140828.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Mon Sep 1 11:55:15 2014 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1409258182 InstallationDate: Installed on 2014-09-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140901-020204) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libstlport.so /android/system/lib/libgccdemangle.so /android/system/lib/libm.so /android/system/lib/libcorkscrew.so /android/system/lib/liblog.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/libc.so /android/system/lib/libcutils.so /android/system/lib/libGLESv2.so /android/system/lib/libEGL.so /android/system/lib/libdsyscalls.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 6 SourcePackage: unity8 StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so Title: unity8-dash crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1363946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650494] [NEW] Un-favoriting a scope after changing the order leaves gaps in Manage dash
Public bug reported: 1. Go to Manage Dash. Make sure you have a few scopes favorited. 2. Long press to start the "edit mode". Move the 2nd scope on the fav list to the last position in favs 3. Leave "edit mode" by pressing the big X button in Manage Dash view. 4. Unfavorite the last scope by tapping star icon. 5. Keep unfavoriting scopes from the bottom of the list. -> Notice how every unfavorited scope leaves a gap on the list ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: 1. Go to Manage Dash. Make sure you have a few scopes favorited. - 2. Long press t start the "edit mode". Move the 2nd scope on the fav list to the last position in favs + 2. Long press to start the "edit mode". Move the 2nd scope on the fav list to the last position in favs 3. Leave "edit mode" by pressing the big X button in Manage Dash view. 4. Unfavorite the last scope by tapping star icon. 5. Keep unfavoriting scopes from the bottom of the list. - -> Notice how every unfavorited scope leaves a gap on the list + -> Notice how every unfavorited scope leaves a gap on the list -- 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/1650494 Title: Un-favoriting a scope after changing the order leaves gaps in Manage dash Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: 1. Go to Manage Dash. Make sure you have a few scopes favorited. 2. Long press to start the "edit mode". Move the 2nd scope on the fav list to the last position in favs 3. Leave "edit mode" by pressing the big X button in Manage Dash view. 4. Unfavorite the last scope by tapping star icon. 5. Keep unfavoriting scopes from the bottom of the list. -> Notice how every unfavorited scope leaves a gap on the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1650494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1244869] Re: Unity home lens restricts results to only files after a search returning only files
I think the cause of this problem are filters, they are apparently not reset correctly in this scenario. If you expand the filters on the 2nd search and select Applications, it works as a workaround too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1244869 Title: Unity home lens restricts results to only files after a search returning only files Status in unity-scope-home package in Ubuntu: Confirmed Bug description: After doing a search in the home lens (the one that returns both files and applications for a search), if your search returned files, then the next search will return files too, even if it should be returning applications. Steps to reproduce: 1. Press the super key to bring up the dash 2. Type a search query that will return only files 3. Go away, perhaps by opening the file you searched for, or pressing the super key again 4. Press the super key to bring up the dash 5. Replace the previous search term with a search query that should return applications 6. Notice that it actually returns only files I expected the 2nd search to return applications (and maybe files) -- but certainly not just files. The workaround is to delete the search query before beginning to type to replace the search term. I have a video showing the error. Let's see if I can attach it... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-scope-home 6.8.2+13.10.20131003-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 26 01:31:47 2013 InstallationDate: Installed on 2013-01-12 (286 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity-scope-home UpgradeStatus: Upgraded to saucy on 2013-10-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1244869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643169] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
See the first error reported by apt-get: "Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again." It seems there is a conflict between a locally installed 'click' python package and the click machinery in the system, causing click hooks to fail during the installation of libunity-scopes deb package. Please remove the locally installed 'click'. ** Changed in: unity-scopes-api (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1643169 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: Invalid Bug description: Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package click (--configure): subprocess installed post-installation script returned error exit status 1 Setting up click-apparmor (0.3.17) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package click-apparmor (--configure): subprocess installed post-installation script returned error exit status 1 Setting up url-dispatcher:amd64 (0.1+16.10.20160816.1-0ubuntu1) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package url-dispatcher:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of ubuntu-app-launch: ubuntu-app-launch depends on click-apparmor; however: Package click-apparmor is not configured yet. dpkg: error processing package ubuntu-app-launch (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-system-settings: ubuntu-system-settings depends on click | ubuntu-snappy-cli; however: Package click is not configured yet. Package ubuntu-snappy-cli is not installed. dpkg: error processing package ubuntu-system-settings (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of url-dispatcher-tools: url-dispatcher-tools depends on url-dispatcher (= 0.1+16.10.20160816.1-0ubuntu1); however: Package url-dispatcher:amd64 is not configured yet. dpkg: error processing package url-dispatcher-tools (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configurationNo apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already of ubuntu-app-launch-tools: ubuntu-app-launch-tools depends on ubuntu-app-launch (= 0.9+16.10.20160928-0ubuntu1); however: Package ubuntu-app-launch is not configured yet. dpkg: error processing package ubuntu-app-launch-tools (--configure): dependency problems - leaving unconfigured Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package libunity-scopes1.0:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of ubuntu-system-settings-online-accounts: ubuntu-system-settings-online-accounts depends on ubuntu-system-settings; however: Package ubuntu-system-settings is not configured yet. dpkg: error processing package ubuntu-system-settings-online-accounts (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of unity8: unity8 depends on ubuntu-system-settings (>= 0.4); however: Package ubuntu-system-settings is not con
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
Please ignore my last comment about this affecting scopes... It was a different root cause afterwards (missing mime database and gdk-pixbuf loaders/cache - https://code.launchpad.net/~stolowski/unity8-session- snap/thumbnailer-fixes/+merge/310756 should fix it). -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
Here is the error returned by thumbnailer in the unity8-dash.log when processing image://thumbnailer/file:/// uris: [2016-11-08:16:59:24.600] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: Handler::checkFinished(): no artwork for thumbnail: /snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart3.png (67,0): NO ARTWORK [2016-11-08:16:59:24.601] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: Handler::checkFinished(): no artwork for thumbnail: /snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/art2.jpg (184,0): NO ARTWORK [2016-11-08:16:59:24.604] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: Handler::checkFinished(): no artwork for thumbnail: /snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart2.png (67,0): NO ARTWORK [2016-11-08:16:59:24.622] :46:33: QML CroppedImageMinimumSourceSize: Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: Handler::checkFinished(): no artwork for thumbnail: /snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart3.png (67,0): NO ARTWORK [2016-11-08:16:59:24.622] :46:33: QML CroppedImageMinimumSourceSize: Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: Handler::checkFinished(): no artwork for thumbnail: /snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/art2.jpg (184,0): NO ARTWORK [2016-11-08:16:59:24.622] :46:33: QML CroppedImageMinimumSourceSize: Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus error: Handler::checkFinished(): no artwork for thumbnail: /snap/unity8-session/x4/usr/lib/x86_64-linux-gnu/unity-scopes/fake_music_scope/albumart2.png (67,0): NO ARTWORK -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-api package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
As discussed no change is needed on scopes api level. Scopes should be using scope_directory() getter to get the base dir and then use all assets paths relative to that; scope_directory() uses $SNAP prefix already. There is a problem though with thumbnailer uris, such as image://thumbnailer/file:///snap/unity8-session/... , which do not yield thumbnails. This might be related to https://bugs.launchpad.net/snappy/+bug/1620635 ** Changed in: unity-scopes-api (Ubuntu) Status: New => Opinion ** Changed in: unity-scopes-api (Ubuntu) Status: Opinion => Invalid -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-api package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
** Changed in: unity-scopes-api (Ubuntu) Importance: High => Undecided -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-api package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
This also affects scopes, we get empty art for thumbnailers uri such as image://thumbnailer/file:///snap/unity8-session/... -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Paweł Stołowski (stolowski) ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => High -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-api package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
I haven't tested the attached branch yet; let's coordinate that since I think you're working with a silo on all this. ** Branch linked: lp:~stolowski/unity-scopes-shell/art-uri-snap-root -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Paweł Stołowski (stolowski) -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap
A quickfix in the shell plugin may fix it for the initial approach (scopes in same snap as the shell), but it gets more complicated when scopes are in separate snaps. -- 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/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1639249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630845] Re: unity8-dash crashed with SIGSEGV in scopes_ng::UbuntuLocationService::update()
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Triaged -- 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/1630845 Title: unity8-dash crashed with SIGSEGV in scopes_ng::UbuntuLocationService::update() Status in unity-scopes-shell package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: unity8-dash crashed with SIGSEGV in scopes_ng::UbuntuLocationService::update() ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160922-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Oct 5 16:03:28 2016 ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2016-10-05 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161005) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcEnviron: LANGUAGE=ru PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f759446f4c5 <_ZN9scopes_ng21UbuntuLocationService6updateEv+213>:mov(%rdi),%rax PC (0x7f759446f4c5) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: scopes_ng::UbuntuLocationService::update() () from /usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QCoreApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: unity8-dash crashed with SIGSEGV in scopes_ng::UbuntuLocationService::update() 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/unity-scopes-shell/+bug/1630845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631172] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... Traceback (most recent call last): File "/usr/bin/click", line 55, in from click import commands ImportError: cannot import name 'commands' [1mdpkg:[0m error processing package libunity-scopes1.0:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 It looks like click failed, perhaps click and/or its dependencies needs upgrading. In any case, libunity-scopes package is innocent here. ** Also affects: click (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-api (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1631172 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in click package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: Invalid Bug description: appears upon logging in ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Oct 5 19:25:54 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-01 (96 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1631172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
Daniel, it seems that all bugs that end up in qFatal() fall into the same bucket.. The error you linked https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb aborts because of Mir: #4 QMessageLogger::fatal (this=0xb6410088 , this@entry=0xb6fa9000, msg=0xb4160e50 "UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is\nrunning, and the correct socket is being used and is accessible. The shell may have\nrejected the incoming connectio"...) at global/qlogging.cpp:636 -- 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/1363946 Title: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: unity8-dash gets into a respawn loop when the selected locale is unavailable. While it's understood that incorrect locale might result in unexpected behaviour, but aborting feels excessive. .log file mentions: ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for client, config file: : unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope c-17178aae: locale::facet::_S_create_c_locale name not ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140828.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Mon Sep 1 11:55:15 2014 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1409258182 InstallationDate: Installed on 2014-09-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140901-020204) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libstlport.so /android/system/lib/libgccdemangle.so /android/system/lib/libm.so /android/system/lib/libcorkscrew.so /android/system/lib/liblog.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/libc.so /android/system/lib/libcutils.so /android/system/lib/libGLESv2.so /android/system/lib/libEGL.so /android/system/lib/libdsyscalls.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 6 SourcePackage: unity8 StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so Title: unity8-dash crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1363946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622423] Re: My activity child link disappears after logged in fitbit account
Ok, I was able to reproduce the issue. I've checked unity-scopes-shell plugin with a debug branch (https://code.launchpad.net/~stolowski/unity-scopes-shell/debug- category-link; packages available here https://code.launchpad.net /~unity-api-team/+archive/ubuntu/dev-build-1/+packages) and it seems to be innocent, according to my debug the category header link is correctly exposed to the QML (the getter for header link gets called when the issue happens, but for some reason is not rendered). Assigning to unity8 project. ** Also affects: unity8 (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/1622423 Title: My activity child link disappears after logged in fitbit account Status in Canonical System Image: New Status in Today Scope: Confirmed Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 15 device name: turbo channel: ubuntu-touch/rc/meizu-pd.en last update: 2016-09-05 03:19:44 version version: 15 version ubuntu: 20160903 version tag: OTA-13-rc version device: 20160824-d33b825 version custom: 20160831-992-8-12 The child arrow link of My Activity session disappears once logged in fitbit account in Today scope, so unable to open My Activity child scope from Today scope Steps to reproduce: 1. Open Today scope and navigate to My Activity session, 2. Existing a child link, tap it will open My Activity scope 2. Tap 'Add your fitbit account' and login with Google account 3. Once logged in, back to Today scope and refresh, check if the child link still exist. Actual results: Once logged in fitbit account, some items of fitbit displayed in session, but the child scope link has gone, unable to open My Activity scope from Today scope If open My Activity scope from manage page by swiping up, blank scope page shown To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1622423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb
Looks like it's related to the changes to settings model made from a separate thread (QtConcurrent is used to update child scopes). ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- 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/1627795 Title: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.14+15.04.20160831.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1627795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627600] Re: unity8-dash failed to launch
Please make sure you have latest everything from xenial overlay ppa (looks like maybe your libunity scopes lib or unity-plugin-scopes are outdated); tested with unity-scope-tool and it works here. This is what I have: ubuntu@ubuntu-xenial:~$ apt-cache policy libunity-scopes1.0 libunity-scopes1.0: Installed: 1.0.7+16.04.20160921-0ubuntu2 Candidate: 1.0.7+16.04.20160921-0ubuntu2 Version table: *** 1.0.7+16.04.20160921-0ubuntu2 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4+16.04.20160402.4-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ubuntu@ubuntu-xenial:~$ apt-cache policy unity-plugin-scopes unity-plugin-scopes: Installed: 0.5.8+16.04.20160921-0ubuntu1 Candidate: 0.5.8+16.04.20160921-0ubuntu1 Version table: *** 0.5.8+16.04.20160921-0ubuntu1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 0.5.7+16.04.20160317-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ubuntu@ubuntu-xenial:~$ apt-cache policy unity8 unity8: Installed: 8.14+16.04.20160922-0ubuntu1 Candidate: 8.14+16.04.20160922-0ubuntu1 Version table: *** 8.14+16.04.20160922-0ubuntu1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 8.12+16.04.20160401-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ubuntu@ubuntu-xenial:~$ ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Incomplete -- 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/1627600 Title: unity8-dash failed to launch Status in unity-scopes-shell package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: failed to run unity8-dash on xenial(amd64). gary@ubuntu:~$ unity8-dash --mousetouch [2016-09-26:14:07:25.432] QQmlApplicationEngine failed to load component [2016-09-26:14:07:25.432] file:///usr/share/unity8//Dash/DashApplication.qml:35 Type Dash unavailable file:///usr/share/unity8//Dash/Dash.qml:20 plugin cannot be loaded for module "Unity": Cannot load library /usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so: (/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so: undefined symbol: _ZN5unity6scopes18SearchListenerBase4pushERKNSt7__cxx114listISt10shared_ptrIKNS0_10FilterBaseEESaIS7_EEE) . gary@ubuntu:~$ apt-cache policy unity8 unity8: Installed: 8.14+16.04.20160922-0ubuntu1 Candidate: 8.14+16.04.20160922-0ubuntu1 Version table: *** 8.14+16.04.20160922-0ubuntu1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 8.12+16.04.20160401-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1627600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492252] Re: Allow direct linking to a Preview via uri
Hi Brian, I started working on the implementation in unity-scopes-shell at the time we discussed this, but it turned out to be more complex than expected. First off, the solution with preview_by_key I suggested above turned out to be a no-go, because it was incompatible with how preview actions work (I should have noticed it early...); so, the way to go is a "result_for_key" method that needs to be implemented by scopes which want to support canned queries requesting a preview. Second off, I've some of that "new approach" implemented in the shell plugin, but we will need changes in plugin<->shell interface too, and for the unity8 shell side of things I need somebody from unity8 team. I hope this will happen at some point, but this enhancement is not a priority at the moment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1492252 Title: Allow direct linking to a Preview via uri Status in Client Developer Experience: New Status in Canonical System Image: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: I can already link to a scopes search via the scope:// protocol but it would be great to be able to link directly to a preview page via a scope:// uri. This would be especially helpful for uApp Explorer to link directly to an app in the official store (rather than the search page like it does now). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1492252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612460] Re: [MIR] unity-scopes-shell
** Branch linked: lp:~stolowski/unity-scopes-shell/fix-bileto-hook- script -- 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/1612460 Title: [MIR] unity-scopes-shell Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues [Quality assurance] * This package has unit tests [Dependencies] * [Standards compliance] * This package uses cmake and is properly translated [Maintenance] * This package is maintained by Canonical and actively in use on the phone images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1612460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked
Yep, the attached MP fixes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked Status in Canonical System Image: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked
** Description changed: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). - This might be related to https://bugs.launchpad.net/qtmir/+bug/1475678 + This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1620297 Title: First scope not rendered until unlocked Status in Canonical System Image: Confirmed Status in qtubuntu package in Ubuntu: New Bug description: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked
** Also affects: canonical-devices-system-image 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/1620297 Title: First scope not rendered until unlocked Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). This might be related to https://bugs.launchpad.net/qtmir/+bug/1475678 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked
Attaching a snippet of unity8-dash.log. Apps scope is my 1st scope. Note, how it's pre-populated @15:03:44 on startup and delivers 29 results: [2016-09-05:15:03:44.547] Pre-populating first scope: "clickscope" I waited ~2 minutes before unlocking the device - this is when I think rendering started (and the scope was set active after unlocking) [2016-09-05:15:05:48.394] file:///usr/share/unity8/Dash/GenericScopeView.qml:390: TypeError: Cannot read property 'defaultMinimumHorizontalSpacing' of null [2016-09-05:15:05:48.790] file:///usr/share/unity8/Dash/GenericScopeView.qml:390: TypeError: Cannot read property 'defaultMinimumHorizontalSpacing' of null [2016-09-05:15:05:49.048] "clickscope" : setActive: true ** Attachment added: "unity8-dash.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1620297/+attachment/4734941/+files/unity8-dash.log -- 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/1620297 Title: First scope not rendered until unlocked Status in unity8 package in Ubuntu: New Bug description: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). This might be related to https://bugs.launchpad.net/qtmir/+bug/1475678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1620297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620297] [NEW] First scope not rendered until unlocked
Public bug reported: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). This might be related to https://bugs.launchpad.net/qtmir/+bug/1475678 ** Affects: unity8 (Ubuntu) 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/1620297 Title: First scope not rendered until unlocked Status in unity8 package in Ubuntu: New Bug description: The pre-populating of first scope on startup (before the screen is unlocked) doesn't seem to be fully working. My early investigation shows that the shell plugin correctly pre- populates scope model on startup when the screen is still locked, but after unlocking scope view is white for 1-2 seconds and only then the page is rendered and all the images are requested, so the perception is as if pre-population didn't work. The perceived performance depends on whether the 1st scope is a local scope (such as Apps) or a scope which needs remote images (and whether the images are already cached by the thumbnailer in the latter case). This might be related to https://bugs.launchpad.net/qtmir/+bug/1475678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1620297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615614] Re: dash is empty, scopes are missing
Hmm, Ubuntu 16.10 has boost 1.61. I agree we are defenseless, but are we sure it was fixed in boost? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1615614 Title: dash is empty, scopes are missing Status in boost package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 dash is empty, scopes are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost/+bug/1615614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615614] Re: dash is empty, scopes are missing
I agree this is a problem, it's an old bug and in fact you'll see a lot of reports about "locale::facet::_S_create_c_locale name not valid" exception thrown by boost - see e.g. the last comment here https://github.com/udoprog/c10t/issues/203 There is nothing we can do at the level it surfaces (scoperegistry in this case) as it aborts the creation of most basic objects we need, so we cannot just catch and ignore it. This problem also manifests itself in unity8-dash (I'm sure it hit it too with your broken locale setup) and the best we could do there was to just prevent the restart-loop of unity8-dash (and leave the dash empty as we cannot instantiate scopes runtime with broken locale). I'm really not sure what more we can do. Adding boost to the bug. ** Also affects: boost (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/udoprog/c10t/issues #203 https://github.com/udoprog/c10t/issues/203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1615614 Title: dash is empty, scopes are missing Status in boost package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 dash is empty, scopes are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost/+bug/1615614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615614] Re: dash is empty, scopes are missing
Looks like it's crashing on invalid locale setup (boost throws exception on us); what is your locale (language) setup? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1615614 Title: dash is empty, scopes are missing Status in unity-scopes-api package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 dash is empty, scopes are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1615614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615004] Re: SmartScopesClient test fails on arm64 in yakkety only
** Description changed: This test fails pretty consistently only on arm64 in yakkety: 22: [ RUN ] SmartScopesClientTest.consecutive_searches 22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.605] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.606] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.607] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.608] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 - 22/111 Test #22: SmartScopesClient ...***Timeout 1500.00 sec + 22/111 Test #22: SmartScopesClient ...***Timeout 1500.00 sec Running main() from gmock_main.cc + + + This test will probably be temporarily disabled on arm64, please enable it back when this bug is fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1615004 Title: SmartScopesClient test fails on arm64 in yakkety only Status in unity-scopes-api package in Ubuntu: New Bug description: This test fails pretty consistently only on arm64 in yakkety: 22: [ RUN ] SmartScopesClientTest.consecutive_searches 22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.605] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory
[Touch-packages] [Bug 1615004] [NEW] SmartScopesClient test fails on arm64 in yakkety only
Public bug reported: This test fails pretty consistently only on arm64 in yakkety: 22: [ RUN ] SmartScopesClientTest.consecutive_searches 22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.605] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.606] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.607] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.608] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22/111 Test #22: SmartScopesClient ...***Timeout 1500.00 sec Running main() from gmock_main.cc ** Affects: unity-scopes-api (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-api in Ubuntu. https://bugs.launchpad.net/bugs/1615004 Title: SmartScopesClient test fails on arm64 in yakkety only Status in unity-scopes-api package in Ubuntu: New Bug description: This test fails pretty consistently only on arm64 in yakkety: 22: [ RUN ] SmartScopesClientTest.consecutive_searches 22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: [2016-08-19 11:02:43.601] INFO: SmartScopesClient_test: SmartScopesClient.search(): GET http://127.0.0.1:1024/demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1.1" 200 1187 22: [2016-08-19 11:02:43.605] ERROR: SmartScopesClient_test: SmartScopesClient::parse_departments(): Error parsing subdepartment of department 'A': unity::LogicException: SmartScopesClient::parse_departments(): missing mandatory department attribute 'canned_query' 22: 127.0.0.1 - - [19/Aug/2016 11:02:43] "GET /demo/search?q=stuff&session_id=session_id&query_id=0&platform=platform HTTP/1
[Touch-packages] [Bug 1612240] [NEW] Please upgrade zmqpp to 4.1.2 git snapshot
Public bug reported: Please update zmqpp to version 4.1.2 with the following patch that I proposed upstream (it got merged into their "develop" branch): https://github.com/zeromq/zmqpp/pull/167/files (alternatively, use master + my patch or develop branch of zmqpp). This will require the current git snapshot of the zmq library (which will be version 4.2 when it's released) - https://github.com/zeromq/libzmq All the above is needed to support the new USE_FD socket option, which will probably be critical for scopes as snaps. ** Affects: zmqpp (Ubuntu) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: New ** Changed in: zmqpp (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zmqpp in Ubuntu. https://bugs.launchpad.net/bugs/1612240 Title: Please upgrade zmqpp to 4.1.2 git snapshot Status in zmqpp package in Ubuntu: New Bug description: Please update zmqpp to version 4.1.2 with the following patch that I proposed upstream (it got merged into their "develop" branch): https://github.com/zeromq/zmqpp/pull/167/files (alternatively, use master + my patch or develop branch of zmqpp). This will require the current git snapshot of the zmq library (which will be version 4.2 when it's released) - https://github.com/zeromq/libzmq All the above is needed to support the new USE_FD socket option, which will probably be critical for scopes as snaps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1612240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606808] Re: scope freezes after login
*** This bug is a duplicate of bug 1607799 *** https://bugs.launchpad.net/bugs/1607799 ** This bug has been marked a duplicate of bug 1607799 Dash freezes after U1 login -- 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/1606808 Title: scope freezes after login Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: scopes which have online-account integrated freezes after login. To reproduce this issue 1. flashing latest image, my image information as following current build number: 394 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-27 12:20:38 version version: 394 version ubuntu: 20160727 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 2. launching youtube scope, click "Log-in" to youtube 3. login with google account and back to youtube scope. 4. scope freezes, there's nothing else I can do with the running scope now. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583067] Re: Lag when favoriting/unfavoriting scopes via Manage Dash
** Branch linked: lp:~stolowski/unity-scopes-shell/favoriting-fixes -- 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/1583067 Title: Lag when favoriting/unfavoriting scopes via Manage Dash Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: There is a noticable lag (2-3 seconds) when unfavoriting and favoriting scopes via Manage Dash. This is probably caused by the fact, that favorites are first written to gsettings, then read back upon gsettings change signal and only then reflected in the display, so there is some I/O and processing of gsettings change when user taps the star. It would be nice to optimize this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603186] Re: Apps scope not shown in the dash (but is installed)
** Branch linked: lp:~stolowski/unity-scopes-shell/favoriting-fixes -- 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/1603186 Title: Apps scope not shown in the dash (but is installed) Status in Canonical System Image: New Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583067] Re: Lag when favoriting/unfavoriting scopes via Manage Dash
** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Paweł Stołowski (stolowski) ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: unity-scopes-shell (Ubuntu) Status: New => 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/1583067 Title: Lag when favoriting/unfavoriting scopes via Manage Dash Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: There is a noticable lag (2-3 seconds) when unfavoriting and favoriting scopes via Manage Dash. This is probably caused by the fact, that favorites are first written to gsettings, then read back upon gsettings change signal and only then reflected in the display, so there is some I/O and processing of gsettings change when user taps the star. It would be nice to optimize this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603186] Re: Apps scope not shown in the dash (but is installed)
** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Paweł Stołowski (stolowski) ** Changed in: unity-scopes-shell (Ubuntu) Status: Triaged => 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/1603186 Title: Apps scope not shown in the dash (but is installed) Status in Canonical System Image: New Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603186] Re: Apps scope not shown in the dash (but is installed)
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603186] Re: Apps scope not shown in the dash (but is installed)
>From the symptoms it seems that the list of favorited scopes got messed up somehow. Did you uninstall unity-scope-click scope before at any point? This list can be (re)set with e.g. $ gsettings set com.canonical.Unity.Dash favorite-scopes "['scope://unity-scope-nearby', 'scope://clickscope']"` or $ gsettings reset com.canonical.Unity.Dash favorite-scopes I think the problem we have is that on the phone we assumed click-scope would never be uninstalled (it's impossible to uninstall it via the UI) and therefore it's impossible to star/unstar it in the UI (it's always "starred"). If however the scope disappears from the system, it's also removed from favorites and there is no way to favorite it back even after manually installing the scope again. Adding unity-scopes-shell as I think it needs to deal with the above scenario. ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scope-click (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => High -- 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/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595120] Re: Scopes do not honour location access setting until device is rebooted
*** This bug is a duplicate of bug 1547573 *** https://bugs.launchpad.net/bugs/1547573 Yes, both these issues are known and were documented (+ bugs opened) in the test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/scopes when the feature was implemented, both causes by issues outside of the scopes api and shell. ** This bug has been marked a duplicate of bug 1547573 trust-store should signal permissions being revoked to services -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1595120 Title: Scopes do not honour location access setting until device is rebooted Status in Canonical System Image: Confirmed Status in unity-scopes-api package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 357 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-22 16:45:25 version version: 357 version ubuntu: 20160622 version device: 20160526-af18709 version custom: 20160504-975-19-6 1. New flashed device, and allow location permission of scopes on first use, check that scopes is enabled and listed in System Settings -->Security & Privacy --> Location 2. Navigate to Today scope or Nearby scope and pull down to refresh, current location information displayed and indicator showing the location services is active 3. Disable location for scopes from System Settings --> Security & Privacy --> Location 4. Back to Today and Nearby scope, pull down to refresh again, the location services still working in Today scope/Nearby scope, no difference than before at all. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
