[Touch-packages] [Bug 1579859] Re: Dash startup time can have a large delay
There are two aspects of these symptomps: 1) black screen with Scopes icon is shown before Dash is loaded and started I believe; 2) white screen (blank) is shown when Dash is loaded and is getting initialized (scope-registry is queried for installed scopes, then first two scopes are loaded, queried & prepopulated to show content immediately after unclock). Both cases are largely affected by the fact that many other processes are started at about the same time and the CPU gets pretty busy. The 2nd case may be impacted if scope uses network (or a slow backend); it's not normally visible unless you unlock really fast (immediately after unity8 start). Attaching bootchart graph (data was collected on the BQ phone from 9 boot sequences). I'm not ruling out any possibility for an improvement, but it's unlikely to be a single thing which suddenly improves the situation, but rather a bunch of smaller improvements here and there (such as perhaps re- arranging how things are initialized in unity8 or elsewhere?). ** Attachment added: "bootchart-bq.png" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579859/+attachment/4697499/+files/bootchart-bq.png -- 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/1579859 Title: Dash startup time can have a large delay Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: While testing fixes for bug #1578283 there was a large discrepancy in how long it took to initialize the scope contents from boot to boot. Often a black screen was shown for up to 10 secs followed by the scope icon then the content, total time well over 12 secs. While there were some crash files at boot that was not consistent with the symptom MX4 proposed v319 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599754] Re: Dash restarts in the middle while refreshing or navigating
Attaching stacktrace of all threads with debug symbols for unity-scopes- api, unity-scopes-shell and unity8-private. I can easily reproduce the problem on frieza with News scope, by just pulling to refresh a couple of times. I wasn't able to reproduce it with Nearby scope. I've attached with gdb to the running dash and my attention was drawn by VerticalJournal::addItemToView; a breakpoint + a simple gdb script to count all calls when this problem is reproduced reveals that it's being called repeatedly in a loop - I've counted 23000+ hits and it's growing (with this bp and gdb overhead the dash runs much slower and I bet it will take a while before it gets killed). This is the backtrace when addItemToView breakpoint gets hit: Breakpoint 2, VerticalJournal::addItemToView (this=0x105a898, modelIndex=0, item=0x1810ef0) at /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/verticaljournal.cpp:129 129 in /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/verticaljournal.cpp $22149 = 22149 #0 VerticalJournal::addItemToView (this=0x105a898, modelIndex=0, item=0x1810ef0) at /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/verticaljournal.cpp:129 #1 0xeac150d2 in AbstractDashView::createItem (this=this@entry=0x105a898, modelIndex=0, asynchronous=asynchronous@entry=false) at /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/abstractdashview.cpp:252 #2 0xeac152c0 in AbstractDashView::addVisibleItems (this=0x105a898, fillFromY=0, fillToY=389, asynchronous=) at /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/abstractdashview.cpp:221 #3 0xeac15332 in AbstractDashView::refill (this=0x105a898) at /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/abstractdashview.cpp:186 #4 0xeac15392 in AbstractDashView::updatePolish (this=0x105a898) at /build/unity8-PQzVl4/unity8-8.12+15.04.20160707/plugins/Dash/abstractdashview.cpp:324 #5 0xec8c6ee0 in QQuickWindowPrivate::polishItems() () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 #6 0xec8a8da2 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 So, is this perhaps related to the Vertical Journal? ** Attachment added: "dash.txt" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1599754/+attachment/4697363/+files/dash.txt -- 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/1599754 Title: Dash restarts in the middle while refreshing or navigating Status in Canonical System Image: Confirmed Status in frieza: New Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: current build number: 15 device name: frieza channel: ubuntu-touch/rc/bq-aquaris-pd.en last update: 2016-07-04 18:00:02 version version: 15 version ubuntu: 20160629 version tag: OTA-12-rc version device: 20160622.0 version custom: 20160624--41-15-vivid Steps: 1.Open news scope 2.Change the number of results in scope setting repeatedly actual: Sometimes, scopes hangs in refreshing state for ~3 minutes, then dash restarts expected: no hang and dash restart To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1599754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598933] Re: ShapeImages in scope ini file is ignored
@James that's corect, I checked this with Albert yesterday and he confirmend the Dash doesn't handle it. It's not totally clear at the moment but it looks like we never intended to support such flag. I also asked design to clarify if we intend to support something like this (in which case Dash needs to be fixed) or if we should remove if from the docs. ** Also affects: ubuntu-ux 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/1598933 Title: ShapeImages in scope ini file is ignored Status in Ubuntu UX: New Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: I've set ShapeImages=false in my scope's ini file, and yet the images are still shaped. In particular, images with a transparent background get a shaped frame drawn around them, which looks terribly ugly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1598933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598680] Re: Share icon isn't discoverable by first glance since bottom bar is hidden
This aspect is fully controlled by unity8, no the scope, so opening it against unity8. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scope-mediascanner (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1598680 Title: Share icon isn't discoverable by first glance since bottom bar is hidden Status in Canonical System Image: Confirmed Status in unity-scope-mediascanner package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: current build number: 375 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-04 10:27:43 version version: 375 version ubuntu: 20160702 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 steps: 1.Go to Video scope 2.Select a local video and open to preview page 3.Check the thumbnal of the video actual: Bottom bar only appears until user tapping on thumbnail, that user cannot find the share icon by first glance. expected: Display the bottom bar by default, like my photo scope did To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598973] Re: No way to set a background image on a scope
This is currently "by design", I'm not sure if there are any plans to support background images, adding to UX. ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: unity-scopes-api (Ubuntu) Status: Confirmed => Incomplete -- 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/1598973 Title: No way to set a background image on a scope Status in Ubuntu UX: New Status in unity-scopes-api package in Ubuntu: Incomplete Bug description: A scope header may have a custom background image (by setting PageHeader.Background in the scope.ini file), but the main body of a scope cannot. One can set a custom background _colour_ on the scope body, but not an image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1598973/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Ok, after some internal discussion about this enhancement the agreed solution is to provide a new "preview_by_key" method (temporary name) which scopes can implement to support canned queries requesting previews. The argument of this method will be a string that acts as a unique key and it's up to the scope what it really is (it can be just a uri). -- 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/1492252 Title: Allow direct linking to a Preview via uri Status in Client Developer Experience: New Status in Canonical System Image: New 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 1492252] Re: Allow direct linking to a Preview via uri
Re-assigning to unity-scopes-api as a new endpoint handler (get result by uri, or get preview by uri depending on how it ends up implemented in the shell plugin) will be needed, plus an enhancement to CannedQuery. ** Changed in: unity-scopes-api (Ubuntu) Status: Invalid => Confirmed ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Wishlist ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (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/1492252 Title: Allow direct linking to a Preview via uri Status in Client Developer Experience: New Status in Canonical System Image: New 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 1496981] Re: Wishlist: Preview widget type queues audio tracks
Hi Peter, thanks for confirming it works. The bug has already been
marked as 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/1496981
Title:
Wishlist: Preview widget type queues audio tracks
Status in unity-scopes-api package in Ubuntu:
Invalid
Bug description:
If more than one audio tracks are put into VariantBuilder object, it would be
nice, if audio tracks will be added into a queue and will be played
automatically in any kind of order, one after the other track.
E.g.:
{
PreviewWidget w1("tracks", "audio");
VariantBuilder builder;
builder.add_tuple({
{"title", Variant("Track #1")},
{"source", Variant("file:///tmp/song1.mp3")},
{"length", Variant(194)}
});
builder.add_tuple({
{"title", Variant("Track #2")},
{"source", Variant("file:///tmp/song2.mp3")},
{"length", Variant(207)}
});
w1.add_attribute_value("tracks", builder.end());
...
}
If song1.mp3 is clicked, song2.mp3 will be played automatically without any
user's click.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1496981/+subscriptions
--
Mailing list: https://launchpad.net/~touch-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
@Brian: Right. That could work under the following assumptions:
- the result uri uniquely identifies a result (currently we don't really
require that nor make any assumptions around that anywhere in the shell as far
as I remember) in the scope which is interested in providing that functionality;
- given a result uri, the scope can produce a *single* result in response;
- that would require a new method in the scopes API ("result_for_uri",
"search_by_uri" or some such) to be implemented by scope author to provide this
new functionality.
- the shell would need to do 2 calls (get the result by uri first, pass it to
preview).
- alternatively, implement this with a new method such as "preview_by_uri", but
I think I'm leaning towards the former approach with result_for_uri as building
the previews is (usually) more complex part of the scope, so requiring scope
authors to think of yet another entry point for previews is probably too much.
--
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/1492252
Title:
Allow direct linking to a Preview via uri
Status in Client Developer Experience:
New
Status in unity-scopes-api package in Ubuntu:
Invalid
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 1595421] Re: Location trusted prompt for Scopes shown immediately after the wizard
** Summary changed: - Location trusted prompt shown immediately after the wizard + Location trusted prompt for Scopes shown immediately after the wizard -- 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/1595421 Title: Location trusted prompt for Scopes shown immediately after the wizard Status in Canonical System Image: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: The trusted prompt for location access for Scopes is shown immediately after the wizard and not after first search or pull-to-refresh initiated by the user as intended. For some reason it happens only if wizard is involved in the boot sequence, and not if trusted prompt for location is just forced by removing .scopesLocationPrompt and trust store db. Looking at the unity8-dash.log file from the first boot after wiping the device, it seems that there is a forced refresh of scopes registry metadata early during the dash startup: [2016-04-23:07:04:42.593] Refreshing scope metadata [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope with id 'com.canonical.scopes.weatherchannel'" [2016-04-23:07:04:42.983] Dispatching search: "com.canonical.scopes.dashboard_dashboard" "" "" [2016-04-23:07:04:42.987] Enabling location updates This calls invalidateResults() and has the same effect as pull-to- refresh. This is most likely caused by the network becoming available & remote scopes getting fetched for the first time, signaling new scopes get available to the shell. To reproduce, reflash with --wipe or perform factory reset. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595421] Re: Location trusted prompt shown immediately after the wizard
** Branch linked: lp:~stolowski/unity-scopes-shell/fix-early-location- prompt -- 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/1595421 Title: Location trusted prompt shown immediately after the wizard Status in Canonical System Image: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: The trusted prompt for location access for Scopes is shown immediately after the wizard and not after first search or pull-to-refresh initiated by the user as intended. For some reason it happens only if wizard is involved in the boot sequence, and not if trusted prompt for location is just forced by removing .scopesLocationPrompt and trust store db. Looking at the unity8-dash.log file from the first boot after wiping the device, it seems that there is a forced refresh of scopes registry metadata early during the dash startup: [2016-04-23:07:04:42.593] Refreshing scope metadata [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope with id 'com.canonical.scopes.weatherchannel'" [2016-04-23:07:04:42.983] Dispatching search: "com.canonical.scopes.dashboard_dashboard" "" "" [2016-04-23:07:04:42.987] Enabling location updates This calls invalidateResults() and has the same effect as pull-to- refresh. This is most likely caused by the network becoming available & remote scopes getting fetched for the first time, signaling new scopes get available to the shell. To reproduce, reflash with --wipe or perform factory reset. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595421] Re: Location trusted prompt shown immediately after the wizard
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => In Progress ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: The trusted prompt for location access for Scopes is shown immediately after the wizard and not after first search or pull-to-refresh initiated by the user as intended. For some reason it happens only if wizard is involved in the boot sequence, and not if trusted prompt for location is just forced by removing .scopesLocationPrompt and trust store db. Looking at the unity8-dash.log file from the first boot after wiping the device, it seems that there is a forced refresh of scopes registry metadata early during the dash startup: [2016-04-23:07:04:42.593] Refreshing scope metadata [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope with id 'com.canonical.scopes.weatherchannel'" [2016-04-23:07:04:42.983] Dispatching search: "com.canonical.scopes.dashboard_dashboard" "" "" [2016-04-23:07:04:42.987] Enabling location updates This calls invalidateResults() and has the same effect as pull-to- refresh. + + This is most likely caused by the network becoming available & remote + scopes getting fetched for the first time, signaling new scopes get + available to the shell. + + To reproduce, reflash with --wipe or perform factory reset. -- 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/1595421 Title: Location trusted prompt shown immediately after the wizard Status in Canonical System Image: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: The trusted prompt for location access for Scopes is shown immediately after the wizard and not after first search or pull-to-refresh initiated by the user as intended. For some reason it happens only if wizard is involved in the boot sequence, and not if trusted prompt for location is just forced by removing .scopesLocationPrompt and trust store db. Looking at the unity8-dash.log file from the first boot after wiping the device, it seems that there is a forced refresh of scopes registry metadata early during the dash startup: [2016-04-23:07:04:42.593] Refreshing scope metadata [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope with id 'com.canonical.scopes.weatherchannel'" [2016-04-23:07:04:42.983] Dispatching search: "com.canonical.scopes.dashboard_dashboard" "" "" [2016-04-23:07:04:42.987] Enabling location updates This calls invalidateResults() and has the same effect as pull-to- refresh. This is most likely caused by the network becoming available & remote scopes getting fetched for the first time, signaling new scopes get available to the shell. To reproduce, reflash with --wipe or perform factory reset. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595421] Re: Location trusted prompt shown immediately after the wizard
** Description changed:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh initiated
- by the user.
-
- This doesn't happen and works as expected if wizard is not involved in
- the boot sequence (e.g. if you force trusted prompt by removing
- /home/phablet/.config/.scopesLocationPrompt and
- ./.local/share/UbuntuLocationService/trust.db and rebooting), this
- suggests it's somehow related to the wizard.
+ by the user as intended. For some reason it happens only if wizard is
+ involved in the boot sequence, and not if trusted prompt for location is
+ just forced by removing .scopesLocationPrompt and trust store db.
Looking at the unity8-dash.log file from the first boot after wiping the
- device, it seems that scopes registry signals a change early on the dash
- startup taking place immediately after pre-populating the scopes
- programmaticaly. This forces invalidateResults() and has the same effect
- as pull-to-refresh. I suspect this may be a race/timing issue caused by
- the fact that the wizard restarts all services like this:
+ device, it seems that there is a forced refresh of scopes registry
+ metadata early during the dash startup:
- QProcess::startDetached(QStringLiteral("sh -c \"initctl emit
indicator-services-end; \
- initctl stop scope-registry; \
- initctl stop smart-scopes-proxy; \
- initctl emit --no-wait indicator-services-start; \
- initctl restart --no-wait maliit-server; \
- initctl restart --no-wait indicator-messages; \
- initctl restart --no-wait unity8-dash\""));
+ [2016-04-23:07:04:42.593] Refreshing scope metadata
+ [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope
with id 'com.canonical.scopes.weatherchannel'"
+ [2016-04-23:07:04:42.983] Dispatching search:
"com.canonical.scopes.dashboard_dashboard" "" ""
+ [2016-04-23:07:04:42.987] Enabling location updates
+
+ This calls invalidateResults() and has the same effect as pull-to-
+ refresh.
** Changed in: unity-scopes-shell (Ubuntu)
Importance: Undecided => High
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Pawel Stolowski (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/1595421
Title:
Location trusted prompt shown immediately after the wizard
Status in unity-scopes-shell package in Ubuntu:
New
Bug description:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh
initiated by the user as intended. For some reason it happens only if
wizard is involved in the boot sequence, and not if trusted prompt for
location is just forced by removing .scopesLocationPrompt and trust
store db.
Looking at the unity8-dash.log file from the first boot after wiping
the device, it seems that there is a forced refresh of scopes registry
metadata early during the dash startup:
[2016-04-23:07:04:42.593] Refreshing scope metadata
[2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope
with id 'com.canonical.scopes.weatherchannel'"
[2016-04-23:07:04:42.983] Dispatching search:
"com.canonical.scopes.dashboard_dashboard" "" ""
[2016-04-23:07:04:42.987] Enabling location updates
This calls invalidateResults() and has the same effect as pull-to-
refresh.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1595421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595421] [NEW] Location trusted prompt shown immediately after the wizard
Public bug reported:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh initiated
by the user.
This doesn't happen and works as expected if wizard is not involved in
the boot sequence (e.g. if you force trusted prompt by removing
/home/phablet/.config/.scopesLocationPrompt and
./.local/share/UbuntuLocationService/trust.db and rebooting), this
suggests it's somehow related to the wizard.
Looking at the unity8-dash.log file from the first boot after wiping the
device, it seems that scopes registry signals a change early on the dash
startup taking place immediately after pre-populating the scopes
programmaticaly. This forces invalidateResults() and has the same effect
as pull-to-refresh. I suspect this may be a race/timing issue caused by
the fact that the wizard restarts all services like this:
QProcess::startDetached(QStringLiteral("sh -c \"initctl emit
indicator-services-end; \
initctl stop scope-registry; \
initctl stop smart-scopes-proxy; \
initctl emit --no-wait indicator-services-start; \
initctl restart --no-wait maliit-server; \
initctl restart --no-wait indicator-messages; \
initctl restart --no-wait unity8-dash\""));
** Affects: unity-scopes-shell (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh initiated
by the user.
This doesn't happen and works as expected if wizard is not involved in
the boot sequence (e.g. if you force trusted prompt by removing
/home/phablet/.config/.scopesLocationPrompt and
./.local/share/UbuntuLocationService/trust.db and rebooting), this
suggests it's somehow related to the wizard.
Looking at the unity8-dash.log file from the first boot after wiping the
device, it seems that scopes registry signals a change early on the dash
startup taking place immediately after pre-populating the scopes
programmaticaly. This forces invalidateResults() and has the same effect
as pull-to-refresh. I suspect this may be a race/timing issue caused by
the fact that the wizard restarts all services like this:
QProcess::startDetached(QStringLiteral("sh -c \"initctl emit
indicator-services-end; \
- initctl stop scope-registry; \
- initctl stop smart-scopes-proxy; \
- initctl emit --no-wait
indicator-services-start; \
- initctl restart --no-wait maliit-server; \
- initctl restart --no-wait
indicator-messages; \
- initctl restart --no-wait
unity8-dash\""));
+ initctl stop scope-registry; \
+ initctl stop smart-scopes-proxy; \
+ initctl emit --no-wait indicator-services-start; \
+ initctl restart --no-wait maliit-server; \
+ initctl restart --no-wait indicator-messages; \
+ initctl restart --no-wait unity8-dash\""));
--
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/1595421
Title:
Location trusted prompt shown immediately after the wizard
Status in unity-scopes-shell package in Ubuntu:
New
Bug description:
The trusted prompt for location access for Scopes is shown immediately
after the wizard and not after first search or pull-to-refresh
initiated by the user.
This doesn't happen and works as expected if wizard is not involved in
the boot sequence (e.g. if you force trusted prompt by removing
/home/phablet/.config/.scopesLocationPrompt and
./.local/share/UbuntuLocationService/trust.db and rebooting), this
suggests it's somehow related to the wizard.
Looking at the unity8-dash.log file from the first boot after wiping
the device, it seems that scopes registry signals a change early on
the dash startup taking place immediately after pre-populating the
scopes programmaticaly. This forces invalidateResults() and has the
same effect as pull-to-refresh. I suspect this may be a race/timing
issue caused by the fact that the wizard restarts all services like
this:
QProcess::startDetached(QStringLiteral("sh -c \"initctl emit
indicator-services-end; \
initctl stop scope-registry; \
initctl stop smart-scopes-proxy; \
initctl emit --no-wait indicator-services-start; \
initctl restart --no-wait maliit-server; \
initctl restart --no-wait indicator-messages; \
initctl restart --no-wait unity8-dash\""));
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1595421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1594880] Re: Location not available after the wizard until reboot
*** This bug is a duplicate of bug 1415029 *** https://bugs.launchpad.net/bugs/1415029 ** Summary changed: - Location settings missing in scope until reboot + Location not available after the wizard until reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1594880 Title: Location not available after the wizard until reboot Status in Canonical System Image: In Progress Status in location-service package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: On this system [1], installed with --bootstrap, I allowed all location related bits as prompted. But, when I looked in a scope (for example NearBy), I found that the scope did not have a location and that the Enable Location settings normally present in scopes was not present. On reboot, everything worked as expected. [1] phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 338 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-06-21 09:59:59 version version: 338 version ubuntu: 20160621 version device: 20160401.1 version custom: 20160504-2-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594880] Re: Location settings missing in scope until reboot
This seems to be a system issue with GPS, location is not available to any apps (I've tried uNav and Here maps) until you reboot after the wizard; dmesg shows this: http://pastebin.ubuntu.com/17685029/ I just confirmed with tvoss this is a known issue. ** Also affects: location-service (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/1594880 Title: Location settings missing in scope until reboot Status in Canonical System Image: In Progress Status in location-service package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: On this system [1], installed with --bootstrap, I allowed all location related bits as prompted. But, when I looked in a scope (for example NearBy), I found that the scope did not have a location and that the Enable Location settings normally present in scopes was not present. On reboot, everything worked as expected. [1] phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 338 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-06-21 09:59:59 version version: 338 version ubuntu: 20160621 version device: 20160401.1 version custom: 20160504-2-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594880] Re: Location settings missing in scope until reboot
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => Critical ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (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/1594880 Title: Location settings missing in scope until reboot Status in Canonical System Image: In Progress Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: On this system [1], installed with --bootstrap, I allowed all location related bits as prompted. But, when I looked in a scope (for example NearBy), I found that the scope did not have a location and that the Enable Location settings normally present in scopes was not present. On reboot, everything worked as expected. [1] phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 338 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-06-21 09:59:59 version version: 338 version ubuntu: 20160621 version device: 20160401.1 version custom: 20160504-2-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page
Hi Enwei, if you tested it previously and you didn't see the issue anymore, then no, no need to re-test, there were no other changes to this branch. -- 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/1590188 Title: Widgets is are in wrong order after posting one comment in Preview Page Status in Canonical System Image: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: I am testing on some golang scopes such as doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban) flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr) After I post one comment and the Preview page refreshes, the order of Preview Widgets is reversed. For example, before I post comment, Art is on the up most position, while after I post comment, Art is the last widget in the page. I can see from the log, the order of widgets is adjusted(art at first is 0, and at last is 15). But i don't know why. AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which could fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page
Ah, my bad, he already did that a few days ago: > Hi Pawel, > I verified on both instagram and flickr scopes. > Here is latest flickr I used, > https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr > Thanks a lot. -- 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/1590188 Title: Widgets is are in wrong order after posting one comment in Preview Page Status in Canonical System Image: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: I am testing on some golang scopes such as doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban) flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr) After I post one comment and the Preview page refreshes, the order of Preview Widgets is reversed. For example, before I post comment, Art is on the up most position, while after I post comment, Art is the last widget in the page. I can see from the log, the order of widgets is adjusted(art at first is 0, and at last is 15). But i don't know why. AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which could fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593035] Re: Scope category layout: vertical-journal does not follow the value of collapsed-rows
** Branch linked: lp:~stolowski/unity-scopes-api/fix-1593035 -- 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/1593035 Title: Scope category layout: vertical-journal does not follow the value of collapsed-rows Status in unity-scopes-api package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Description: Scope vertical-journal layout does not follow the value of collapsed-rows. Reproduce Steps: a) Implement a scope with category-layout: vertical-journal b) Add collapsed-rows property, for instance "collapsed-rows": 1 c) Observe the showing of the scope Expected Result: Scope will collapsed the rows as only 1 row. Actual Result: Scope shows all the results with several rows. Occurrence: 10/10 (100%) Hardware Information: current build number: 442 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-05-19 19:28:28 version version: 442 version ubuntu: 20160518.1 version device: 20160401.1 version custom: 20160518.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1593035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593035] Re: Scope category layout: vertical-journal does not follow the value of collapsed-rows
** Changed in: unity-scopes-api (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1593035 Title: Scope category layout: vertical-journal does not follow the value of collapsed-rows Status in unity-scopes-api package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Description: Scope vertical-journal layout does not follow the value of collapsed-rows. Reproduce Steps: a) Implement a scope with category-layout: vertical-journal b) Add collapsed-rows property, for instance "collapsed-rows": 1 c) Observe the showing of the scope Expected Result: Scope will collapsed the rows as only 1 row. Actual Result: Scope shows all the results with several rows. Occurrence: 10/10 (100%) Hardware Information: current build number: 442 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-05-19 19:28:28 version version: 442 version ubuntu: 20160518.1 version device: 20160401.1 version custom: 20160518.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1593035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593035] Re: Scope category layout: vertical-journal does not follow the value of collapsed-rows
I'll update the documentation of CategoryRenderer as collapsed-rows is not supported in the vertical-journal. ** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Medium ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) ** Changed in: unity-scopes-api (Ubuntu) Status: New => Confirmed ** Changed in: unity8 (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/1593035 Title: Scope category layout: vertical-journal does not follow the value of collapsed-rows Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Description: Scope vertical-journal layout does not follow the value of collapsed-rows. Reproduce Steps: a) Implement a scope with category-layout: vertical-journal b) Add collapsed-rows property, for instance "collapsed-rows": 1 c) Observe the showing of the scope Expected Result: Scope will collapsed the rows as only 1 row. Actual Result: Scope shows all the results with several rows. Occurrence: 10/10 (100%) Hardware Information: current build number: 442 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-05-19 19:28:28 version version: 442 version ubuntu: 20160518.1 version device: 20160401.1 version custom: 20160518.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1593035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467886] Re: expandable widget cannot collapse widgets to the number defined by "collapsed-widgets"
** Branch linked: lp:~stolowski/unity-scopes-api/fix-expandable-widget-
doc
** Changed in: unity-scopes-api (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1467886
Title:
expandable widget cannot collapse widgets to the number defined by
"collapsed-widgets"
Status in unity-scopes-api package in Ubuntu:
In Progress
Status in unity-scopes-shell package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
Invalid
Bug description:
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04/previewwidgets/
I tried to used the example code shown in the above link:
PreviewWidget expandable("exp", "expandable");
expandable.add_attribute_value("title", Variant("This is an expandable
widget"));
expandable.add_attribute_value("collapsed-widgets", Variant(0));
PreviewWidget w1("w1", "text");
w1.add_attribute_value("title", Variant("Subwidget 1"));
w1.add_attribute_value("text", Variant("A text"));
PreviewWidget w2("w2", "text");
w2.add_attribute_value("title", Variant("Subwidget 2"));
w2.add_attribute_value("text", Variant("A text"));
expandable.add_widget(w1);
expandable.add_widget(w2);
regardless of whatever number is defined in "collapsed-widgets", it
always shows all of the widgets there.
Thanks & best regards,
XiaoGuo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1467886/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446216] Re: [Dash] CategoryHeaderBackground is not implemented
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Medium -- 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/1446216 Title: [Dash] CategoryHeaderBackground is not implemented Status in unity-scopes-api package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: Invalid Bug description: CategoryHeaderBackground is supposed to be change appearance but has no effect. Quickly checking code revealed that it hasn't been implemented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1446216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398369] Re: SmartScopesProxy should allow more detailed/verbose logging
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Medium ** Changed in: unity-scopes-api (Ubuntu) Status: New => Triaged -- 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/1398369 Title: SmartScopesProxy should allow more detailed/verbose logging Status in unity-scopes-api package in Ubuntu: Triaged Bug description: Like, when doing restart smart-scopes-proxy LOGGING=DEBUG It should send to log more information, for example not only what it's requesting from the server, but also the responses, with proper timestamps. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1398369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467886] Re: expandable widget cannot collapse widgets to the number defined by "collapsed-widgets"
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Pawel Stolowski (stolowski)
** Changed in: unity8 (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-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1467886
Title:
expandable widget cannot collapse widgets to the number defined by
"collapsed-widgets"
Status in unity-scopes-api package in Ubuntu:
Confirmed
Status in unity-scopes-shell package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
Invalid
Bug description:
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04/previewwidgets/
I tried to used the example code shown in the above link:
PreviewWidget expandable("exp", "expandable");
expandable.add_attribute_value("title", Variant("This is an expandable
widget"));
expandable.add_attribute_value("collapsed-widgets", Variant(0));
PreviewWidget w1("w1", "text");
w1.add_attribute_value("title", Variant("Subwidget 1"));
w1.add_attribute_value("text", Variant("A text"));
PreviewWidget w2("w2", "text");
w2.add_attribute_value("title", Variant("Subwidget 2"));
w2.add_attribute_value("text", Variant("A text"));
expandable.add_widget(w1);
expandable.add_widget(w2);
regardless of whatever number is defined in "collapsed-widgets", it
always shows all of the widgets there.
Thanks & best regards,
XiaoGuo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1467886/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568035] Re: cannot change department from code
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Wishlist -- 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/1568035 Title: cannot change department from code Status in canonical-scopes-project: New Status in Ubuntu UX: New Status in unity-scopes-api package in Ubuntu: New Bug description: There is no ability to change the current department from code. This means that the scope cannot "do the right thing" when a user enters a query string in some cases. For example, suppose a scope has departments that represent a web api's departments. And suppose the web api does not support searching inside a department but only supports searches over the whole site. What is the scope developer to do when the user is in a department *and* they enter a query string? Because there is no way now to change the department (perhaps to a department named "Search Results"), the dev *must* return results in the current department, which is incorrect. 500px web api and our 500px scope is like this. 500px has "streams" like "Editors", "Fresh today" etc. The scope displays these as departments. However, the 500px web api has no api to provide search results limited to a stream. Therefore when a user is in a department, for example "Fresh Today" and they enter a search string, the results are in fact not limited to Fresh Today but they are displayed in the Fresh Today department, which is not correct. It is possible (and the proposed the 1.0 version of the 500px scope does this) to avoid the problem by applying the search query string to the department's results. So for example if the search was "strawberry" and the user was in "Fresh Today" department, the scope only displays received "Fresh Today" results that contain "strawberry". But this is sub-optimal because the scope needs to keep querying the api to get more and Fresh Today results trying to find matches, which takes time and may not find a match. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-scopes-project/+bug/1568035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568054] Re: package libunity-scopes1.0 1.0.4+16.04.20160317-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Looking at the DpkgTerminalLog, this was a problem with click hooks or something related affecting apt, which resulted in a couple of bug reports like this one in other projects. This was a transient issue unrelated to unity-scopes-api and it was fixed, so closing this bug. ** 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/1568054 Title: package libunity-scopes1.0 1.0.4+16.04.20160317-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: Invalid Bug description: happened on login ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0 1.0.4+16.04.20160317-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 8 10:04:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-03-30 (9 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.4+16.04.20160317-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-03-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1568054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540876] Re: Not all results recieved when there is a lot of them (>=3000?)
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Low -- 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/1540876 Title: Not all results recieved when there is a lot of them (>=3000?) Status in unity-scopes-api package in Ubuntu: In Progress Bug description: It looks like ZMQ high water-mark limits the number of results that can succesfuly be received by a client to something around 2000; this may depend on the result size and delays between pushes though. With 3000 results in my test code I was receiving approximately 1900, the remainder was dropped on the floor. While these numbers are probably more than we will ever need, it may be worth looking into it. Perhaps ZMQ queue size can be increased, also a meaningful error in the logs about hitting such cases would be nice (if possible at all). I'll add a pointer to a sample test case from unity-scopes-shell at a later time, please contact me if I forget to do so ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1540876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585654] Re: surfacing_cache put in .local/share/unity-scopes/unconfined/SSRegistry
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Medium -- 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/1585654 Title: surfacing_cache put in .local/share/unity-scopes/unconfined/SSRegistry Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: While testing remote scopes on the phone today I noticed a fresh .surfacing_cache file created in the .local/share/unity- scopes/unconfined/SSRegistry directory. Looking at the contents it contains the data from a remote scope I used *last* (it gets overwritten each time I switch to a different remote scope). SmartScope.cpp code doesn't currently push surfacing results (it could be a nice idea to do that if we get server error?), so creating that file and overwriting it each and every time another remote scope is opened is wasteful. We should either disable this functionality completely for remote scopes or store unique file for every remote scope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1585654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502282] Re: "unknown" connectivity status problematic
Marking invalid in scopes API since the problem was in the shell plugin and got fixed. ** Changed in: unity-scopes-api (Ubuntu) Status: Confirmed => 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/1502282 Title: "unknown" connectivity status problematic Status in The Savilerow project: New Status in unity-scopes-api package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: metadata provides a scope a network connectivity status enum with three possible states: * connected * disconnected * unknown Sometimes unknown is the current state. This is quite problematic because in general a scopes that queries the network (that is, most scopes) need to know whether there is network or is not network and depending on this either make the network queries or display an error message. A status of unknown connectivity leaves the scope with no valid option: * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily * the scope could assume the network is up, but this is dangerous if it is not up To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566952] Re: Push method for filters should be updated
** Branch linked: lp:~stolowski/unity-scopes-api/update-push-filters -- 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/1566952 Title: Push method for filters should be updated Status in unity-scopes-api package in Ubuntu: In Progress Bug description: The push(filters, filterState) method should be marked deprecated. The doc for this method should be updated to say that sending modified filterState back to the UI has no effect. A new overloaded push method that only takes filters should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1566952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421802] Re: scopes not updated as often as expected
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Medium -- 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/1421802 Title: scopes not updated as often as expected Status in Ubuntu Rest Scopes: New Status in unity-scopes-api package in Ubuntu: Triaged Bug description: When using the weather channel scope, I find it doesn't update when I expect. Eg, someone asked me what the temp was going to be and I said '46'. She responded with "What?!? No way, I heard it was supposed to be in the 70s!". Then I responded "oh, let me swipe down-- yes, there we go, 76". Seems that it should maybe update automatically after screen unlock and/or coming back in from another scope. Other weather apps seem to be able to do this fine. Perhaps this automatic updating would be something a scope could opt in to? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1421802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324138] Re: Unreachable smartscopesproxy causes timeout exception in the client
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Low -- 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/1324138 Title: Unreachable smartscopesproxy causes timeout exception in the client Status in unity-scopes-api package in Ubuntu: Triaged Bug description: If scopesregistry is configured to use smartscopesproxy, but smartscopesproxy is not running, then running a client such as unity- scope-tool results in a 300 ms timeout exception both in scopesregistry and in the client, and even local scopes are not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1324138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421802] Re: scopes not updated as often as expected
** Changed in: unity-scopes-api (Ubuntu) Status: New => Triaged -- 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/1421802 Title: scopes not updated as often as expected Status in Ubuntu Rest Scopes: New Status in unity-scopes-api package in Ubuntu: Triaged Bug description: When using the weather channel scope, I find it doesn't update when I expect. Eg, someone asked me what the temp was going to be and I said '46'. She responded with "What?!? No way, I heard it was supposed to be in the 70s!". Then I responded "oh, let me swipe down-- yes, there we go, 76". Seems that it should maybe update automatically after screen unlock and/or coming back in from another scope. Other weather apps seem to be able to do this fine. Perhaps this automatic updating would be something a scope could opt in to? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1421802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381891] Re: Setting invalid widget attribute does not raise exception
The problem we have is we deliberately decided not to do any validation
on the scopes API side and leave it up to the unity (even the shell
plugin doesn't care much about what's inside the preview widgets).
The downside is in many cases scope author is clueless if widget doesn't
show up or look as expected.
On the upside, support for new widgets can be added to the shell or
existing widgets can be enhanced to support new attributes without
affecting the lower layers.
Now, the problem of not having a clue as a scope author if something
goes wrong is and important issue, so perhaps we should look for a
middle ground. How about adding a simple validation and only output cerr
warnings if we see something we don't know (and never throw, unless we
find cases where we really know thw widget is totally broken)?
--
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/1381891
Title:
Setting invalid widget attribute does not raise exception
Status in unity-scopes-api package in Ubuntu:
New
Bug description:
Suppose I do:
PreviewWidget desc("summary_col", "text");
desc.add_attribute_value("test", Variant("This is the text for the widget"));
Did you spot the error? The attribute being set is "test", but it
should be "text". There is no indication that I'm doing something
impossible, and I'm left scratching my head why nothing renders.
It might be better to raise InvalidArgumentException here?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1381891/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566952] Re: Push method for filters should be updated
** Description changed: The push(filters, filterState) method should be marked deprecated. The - doc for this method should be updated to say it's only useful for the UI - or for clients (aggregator scopes) and sending modified filterState back - to the UI has no effect. + doc for this method should be updated to say that sending modified + filterState back to the UI has no effect. A new overloaded push method that only takes filters should be added. ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Medium ** Changed in: unity-scopes-api (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1566952 Title: Push method for filters should be updated Status in unity-scopes-api package in Ubuntu: In Progress Bug description: The push(filters, filterState) method should be marked deprecated. The doc for this method should be updated to say that sending modified filterState back to the UI has no effect. A new overloaded push method that only takes filters should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1566952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366870] Re: PreviewModel::loaded and ::processingAction don't seem to change
This doesn't seem to be the case anymore, it got fixed with all the changes to preview models. ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Fix Released -- 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/1366870 Title: PreviewModel::loaded and ::processingAction don't seem to change Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: After the initial preview has loaded, neither of the mentioned properties seem to change. Steps to reproduce: 1. go to app store 2. choose an app that you don't have installed 3. wait for the bottom activity indicator to stop 4. tap on the Install button 5. wait for the progress bar to appear 6. wait for the progress bar to reach 100% Expected: 4. bottom activity indicator should start as soon as you tap Install 6. --||-- when the installation completes Current: 4. there's a no-feedback delay before 5. 6. there's a no-feedback delay before the preview reloads ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-plugin-scopes 0.5.4+14.10.20140902-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Mon Sep 8 17:54:56 2014 InstallationDate: Installed on 2014-09-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140908-123005) SourcePackage: unity-scopes-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1366870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457535] Re: [Scopes] Expected Scopes to automatically refresh after any changes being made
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Triaged ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1457535 Title: [Scopes] Expected Scopes to automatically refresh after any changes being made Status in unity-scopes-shell package in Ubuntu: Triaged Bug description: "These included: - Select and deselect content options from the Scope settings. Eg. testers changed some content settings on the Scope (eg. untick fitbit from the 'Today' Scope, remove certain news sources from the News Scope), however these changes were not reflected on the Scopes. They did not know they need to manually refresh the page by using a pulling down gesture. - Any actions that would have an effect on Scopes, eg. delete a calendar event entry - Reconnect to the Internet" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1457535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428591] Re: Dash crashes when trying to authenticate soundcloud scope with google, empty auth page
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-scope-soundcloud Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1428591 Title: Dash crashes when trying to authenticate soundcloud scope with google, empty auth page Status in Canonical System Image: Confirmed Status in Unity SoundCloud Scope: Invalid Status in webapps-sprint: Fix Committed Status in ubuntu-system-settings-online-accounts package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: 1. Go to Soundcloud scope 2. Hit Log-in to SoundCloud button 3. Choose 'Sign in with Google' on the SoundCloud auth page 4. Fill in google account credentials, confirm soundcloud permissions Result: a blank page with 'Cancel' button, no way to navigate back, hitting it crashes the dash (I couldn't get a usable backtrace). NB, this works fine when authenticating using a genuine Soundcloud account. It seems like authenticating via Google is causing the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1428591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587097] Re: No UI feedback after saving a review change
** Changed in: unity-scope-click (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => 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/1587097 Title: No UI feedback after saving a review change Status in Canonical System Image: New Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: Test case. - In System Settings > Accounts, log in Ubuntu One. - Open the Ubuntu Store. - Install a new app. - Post a review with ratings. - Edit the review and save it. Expected result. - The text edit field and the button are hidden, the new text is displayed and edit button appears. Actual result. - Text edit field and save button are displayed. Scrolling down and up shows the text and the edit button. Checked with image 345 from ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512128] Re: System reboot when granting access to location on arale
** Summary changed: - System reboot when granting access to location + System reboot when granting access to location on arale -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1512128 Title: System reboot when granting access to location on arale Status in Canonical System Image: Confirmed Status in trust-store package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Expired Bug description: arlae rc-proposed (not sure this is really browser issue but its what i was using) Open maps.google.com Webbroser prompts to allow access for the page to my location, allow Trust store prompt to allow access for webbrowser (I thought I had already granted it int he past), allow The phone hangs for a few seconds then reboots. The Meizu logo was shown and it vibrated so not just a unity restart To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512128] Re: System reboot when granting access to location
This seems to be affecting the changes now in silo 65 (unity8-dash runs confined and requests location access shortly after boot), and it has been reproduced without much problem on two arale systems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1512128 Title: System reboot when granting access to location Status in trust-store package in Ubuntu: Expired Status in webbrowser-app package in Ubuntu: Expired Bug description: arlae rc-proposed (not sure this is really browser issue but its what i was using) Open maps.google.com Webbroser prompts to allow access for the page to my location, allow Trust store prompt to allow access for webbrowser (I thought I had already granted it int he past), allow The phone hangs for a few seconds then reboots. The Meizu logo was shown and it vibrated so not just a unity restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trust-store/+bug/1512128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518583] Re: [Ubuntu Store Scope] "show all" only shows first 100 results
*** This bug is a duplicate of bug 1394480 *** https://bugs.launchpad.net/bugs/1394480 ** This bug has been marked a duplicate of bug 1394480 [scopes] Need a mechanism to load more query results -- 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/1518583 Title: [Ubuntu Store Scope] "show all" only shows first 100 results Status in Canonical System Image: Confirmed Status in Click Package Index: Confirmed Status in unity-scope-click package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Triaged Bug description: In category news & magazines there are not displayed all apps when you click on display all. Unrated apps are currently not displayed. But maybe there's a app count limit. If you search for the name of an undisplayed app it's found. Example: "Tagesanzeiger" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421802] Re: scopes not updated as often as expected
We do have a (limited) support for automatic updating via "TTL" mechanism in the shell plugin; scopes opt in for it by declaring ttl value (small = 30 seconds, medium = 5 minutes, large = 1 hour) in their config file. We could use it here, only bit missing is to support it for remote scopes - make them declare it in the json here https://dash.ubuntu.com/smartscopes/v2/remote-scopes and make smart scopes client code parse it and expose in scope metadata (so that shell can use it). ** Also affects: ubuntu-rest-scopes Importance: Undecided Status: New ** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity-scopes-shell (Ubuntu) -- 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/1421802 Title: scopes not updated as often as expected Status in Ubuntu Rest Scopes: New Status in unity-scopes-api package in Ubuntu: New Bug description: When using the weather channel scope, I find it doesn't update when I expect. Eg, someone asked me what the temp was going to be and I said '46'. She responded with "What?!? No way, I heard it was supposed to be in the 70s!". Then I responded "oh, let me swipe down-- yes, there we go, 76". Seems that it should maybe update automatically after screen unlock and/or coming back in from another scope. Other weather apps seem to be able to do this fine. Perhaps this automatic updating would be something a scope could opt in to? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1421802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417780] Re: Refreshing scopes data when using a poor connection produces a really bad user experience
The bug #1238979 improves the situation with updates to the results model, but it doesn't solve the problem of poor connection. For this to be possible I think we will need cooperation from scopes, because only the scopes know if all the data they serve comes from network and if old results should be preserved if network is not available. Scopes currently receive connectivity status with every search, so they can use push_surfacing_results_from_cache() method of the SearchReply to push the old results again without any extra work. We could make it even easier for scopes to handle this by enhancing CompletionDetails in scopes API with a new status such as InternetRequied (displays appropriate banner to warn the user) or InternetRequiredAndKeepTheResults (banner + keep old results on the screen) - but are easy to implement in the shell, but the bulk of work would be to update scopes to use it. ** 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/1417780 Title: Refreshing scopes data when using a poor connection produces a really bad user experience Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: (Not sure if this is the best package/project to cover this bug, feel free to change it) current build number: 224 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-29 18:53:09 version version: 224 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 The scopes content disappears completely when you try to refresh it when using a poor internet connection, because it blanks the previous content without giving any new ones (until you get a proper connection again). This produces a really bad user experience because the user ends up with a set of blank scopes, without any content (while the previous data could be useful in some way). As a user I'd expect the data to be dynamically updated (visually at least) as you get them, with a proper notification for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394614] Re: Cached results stay in scopes even with no internet
As commented earlier by Michi, caching is generally nice and we actually put effort recently to display cached results (if possible) in Ubuntu store scope. Closing this bug. ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Invalid -- 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/1394614 Title: Cached results stay in scopes even with no internet Status in unity-scopes-api package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: I am testing the latest image and as per the test plan, if internet is disabled there are cached results in a scope they should vanish as we refresh the scope but right now that's not the case. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 15:06:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387948] Re: Enabling flight mode does not refresh scopes
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Triaged ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1387948 Title: Enabling flight mode does not refresh scopes Status in unity-scopes-shell package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Reboot the phone while in flight mode, with some aggregators favourited (such as Music, Video, and YouTube). After reboot, swiping to any of the aggregators displays an empty screen. That's as expected, seeing that the network is not available. It would be nice though to have some indication as to *why* nothing is shown. Now enable flight mode again and swipe to any of the three blank scopes. They are still blank, and I have to do a manual refresh to get them to work again. It might be nice to check whether the network has been up and down since last time a scope was seen by the user and, if so and there are either no results, or results that are too old, do a refresh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1387948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492287] Re: FTBFS with Python 3.5 as supported version in Wily
There is now a slightly more complicated check in the CMakeLists.txt:
# Ubuntu xenial needs python 3.5
if(${DISTRIBUTION} MATCHES "vivid" OR ${DISTRIBUTION} MATCHES "wily")
find_package(PythonLibs 3.4 REQUIRED)
find_package(Boost COMPONENTS python-py34 REQUIRED)
else()
find_package(PythonLibs 3.5 REQUIRED)
find_package(Boost COMPONENTS python-py35 REQUIRED)
endif()
I'm not sure if there is a better fix for this?
** Changed in: unity-scopes-shell (Ubuntu)
Status: Confirmed => 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/1492287
Title:
FTBFS with Python 3.5 as supported version in Wily
Status in unity-scopes-shell package in Ubuntu:
Incomplete
Bug description:
In Wily, we enable Python 3.5 as a supported (but not default) Python
3 version. We have a PPA where we make Python 3.5 the default
version. unity-scopes-shell fails to build in this PPA. Here is the
buildlog:
https://launchpadlibrarian.net/216373229/buildlog_ubuntu-wily-amd64
.unity-scopes-shell_0.5.5%2B15.10.20150826-0ubuntu1_BUILDING.txt.gz
A cursory look seems to indicate that the cmake files aren't prepared
to handle the case where Python 3.5 is the default Python 3 version.
A local build of the wily package, where 3.5 is supported but not
default also FTBFS but in a different way. I will attach the local
buildlog for that failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1492287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453795] Re: Apps can't change their own app icon
** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1453795 Title: Apps can't change their own app icon Status in unity-scope-click package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Some apps would be more useful and/or delightful if they could change the appearance of their own app icon, even when the app is not running. For a couple of apps this is important: - It is misleading for the Calendar app icon to show a date that isn't the current date (bug 1362962). - It is also misleading for the Clock app icon to show a time that isn't the current time (bug 1362964). For other apps it would be just nice to have: - A Weather app would be more useful if its icon showed the current weather (against a sky reflecting the time of day) without you having to open it. - The Gallery icon could include thumbnails of your most recent 3~4 photos. - A Reminders icon could miniaturize the start of the frontmost note (similar to Nautilus's icons for text files), which might occasionally save you from opening the app. This might be achieved by having an API for any app to update its own icon on a timer -- for example the Weather app might ask for the opportunity to update its icon every 30 minutes. Or it might be achieved by hard-coding Clock and Calendar icon updating inside Unity. (This would probably be necessary for a Clock icon to have an updating second hand.) Or there might be a combination of both approaches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1453795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458235] Re: [scopes] Allow users to set arbitrary location for scopes.
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => Triaged ** 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/1458235 Title: [scopes] Allow users to set arbitrary location for scopes. Status in Ubuntu UX: Fix Committed Status in unity-scopes-shell package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Currently I can't set my location manually for any scope. They get it somehow automatically, most of the time wrongly. It would be nice if a user could somehow select the location he/she wants. -- UX Comment -- This will be soon possible with the 'Location filter widget' - currently under development. For further information please refer to the Filter wisgets in Scopes design specification: https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1458235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378185] Re: Sometimes, header and departments combobox disappear
Hi Leo, I haven't encountered this bug and both unity-scopes-shell and unity8 changed a lot in this area since you reported it. Marking this incomplete, please re-open if you can still reproduce (and in such case please take note of the scope which exhibited the issue). Thanks. ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => 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/1378185 Title: Sometimes, header and departments combobox disappear Status in unity-scopes-shell package in Ubuntu: Incomplete Bug description: This has happened to me twice on krillin #87 while testing silo 18 with unity-plugin-scopes 0.5.4+14.10.20141002.1-0ubuntu1 http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm=landing-018 See the attached screenshot. What I did in this case was to install 2ubuntu. Then got back to the home screen clicking the back button on the header. The header appears again if I swipe down the dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1378185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364342] Re: Allow a rootless navigation structure
With filters support this could be re-designed to use option-selector filters:
- one option selector filter with new releases, top albums, top tracks, genres
in it; selecting 'genres' creates additional option-selector filter with the
list of genres in it.
- two option selector filters displayed all the time: one with new releases,
top albums, top tracks, the other with the list of genres - makes sense so long
as 7digital api allows browsing new releases/top albums/tracks and filtering by
genre at the same time.
This is just an idea to consider. Allowing rootless departments will
require significant investement in terms of implementation.
** 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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1364342
Title:
Allow a rootless navigation structure
Status in unity-scopes-shell package in Ubuntu:
Triaged
Status in unity8 package in Ubuntu:
Triaged
Bug description:
Currently, the 7digital scope is returning this structure for the
categories/departments/navigation:
{'canned_query': 'scope://com.canonical.scopes.sevendigital',
'label': 'All categories',
'subdepartments': [{'canned_query':
'scope://com.canonical.scopes.sevendigital?dep=newreleases',
'has_subdepartments': False,
'label': 'New releases'},
{'canned_query':
'scope://com.canonical.scopes.sevendigital?dep=topalbums',
'has_subdepartments': False,
'label': 'Top albums'},
{'canned_query':
'scope://com.canonical.scopes.sevendigital?dep=toptracks',
'has_subdepartments': False,
'label': 'Top tracks'},
{'canned_query':
'scope://com.canonical.scopes.sevendigital?dep=genres',
'has_subdepartments': True,
'label': 'Genres'}]}
However, Design requested for this structure to be rootless, to don't
have a "All categories" root in the beginning. Currently, if the
server returns the needed structure, it doesn't work ok.
Talking with Pawel and Albert they agreed works needs to be done in
this project for this to be possible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1364342/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509591] Re: package unity-plugin-scopes 0.5.4+15.04.20150410.2-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Indeed, that was a problem with click/apport, unrelated to unity-scopes-shell. ImportError: libapt-pkg.so.4.16: cannot open shared object file: No such file or directory and looking at this other bug report, it was fixed long time ago. Closing. ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => 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/1509591 Title: package unity-plugin-scopes 0.5.4+15.04.20150410.2-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: on 15.10 upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: unity-plugin-scopes 0.5.5+15.10.20150924-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Thu Oct 22 21:00:16 2015 DuplicateSignature: package:unity-plugin-scopes:0.5.4+15.04.20150410.2-0ubuntu1:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2011-04-22 (1645 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: unity-scopes-shell Title: package unity-plugin-scopes 0.5.4+15.04.20150410.2-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1509591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page
** Branch linked: lp:~stolowski/unity-scopes-shell/fix-preview-updates -- 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/1590188 Title: Widgets is are in wrong order after posting one comment in Preview Page Status in Canonical System Image: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: I am testing on some golang scopes such as doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban) flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr) After I post one comment and the Preview page refreshes, the order of Preview Widgets is reversed. For example, before I post comment, Art is on the up most position, while after I post comment, Art is the last widget in the page. I can see from the log, the order of widgets is adjusted(art at first is 0, and at last is 15). But i don't know why. AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which could fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page
** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity8 (Ubuntu) ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => High ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1590188 Title: Widgets is are in wrong order after posting one comment in Preview Page Status in Canonical System Image: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: I am testing on some golang scopes such as doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban) flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr) After I post one comment and the Preview page refreshes, the order of Preview Widgets is reversed. For example, before I post comment, Art is on the up most position, while after I post comment, Art is the last widget in the page. I can see from the log, the order of widgets is adjusted(art at first is 0, and at last is 15). But i don't know why. AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which could fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590188/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Also, can you attach unity8-dash.log when this happens? I wonder why you don't see a blank dash instead... -- 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 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
Hi Timo, how did you manage to end up with a broken locale setup? -- 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 1398843] Re: scope API - department does not reset on filters' change
This is by design, departments (if present) act as top-level navigation, filters are secondary means of narrowing data down inside departments, not vice versa. This is the way it works in major online shops and we haven't yet encountered a case where this approach doesn't work. Marking as 'won't fix' but please provide more details about your case if you think this is a serious limitation which cannot be solved by other means (more filters, separate scopes etc.). ** Changed in: unity-scopes-api (Ubuntu) Status: New => Won't Fix ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Won't Fix -- 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/1398843 Title: scope API - department does not reset on filters' change Status in unity-scopes-api package in Ubuntu: Won't Fix Status in unity-scopes-shell package in Ubuntu: Won't Fix Status in unity8 package in Ubuntu: Invalid Bug description: Let's assume one decides to have a different tree of departments depending on which filter is selected. If i select a department(e.g. with id="80" and not present in the filter2), and then i select filter2, the following exception is thrown: ScopeBase::run(): unity::LogicException: SearchReplyImpl::register_departments(): Failed to validate departments: unity::LogicException: DepartmentImpl::validate_departments(): current department '80' doesn't match any of the subdepartments of parent '' However, if i select again filter2, the department resets correctly to the root. It seems like the new query on the filter selection does not update the departments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1398843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419829] Re: [Scope] location settings are enabled by default
This is now in silo 65 and the test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/scopes has been updated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1419829 Title: [Scope] location settings are enabled by default Status in Canonical System Image: In Progress Status in Ubuntu UX: Opinion Status in location-service package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: This is in contrast to the rest of the system where user have to explicitly grant access right upfront. Possible solution would be to add a new page in phone setup wizard asking for whether scopes are allowed to use location or not and then applying this to individual scope location settings. UX comment- Potential new project: When scopes will be launched as apps, we'll probably need some coach marks // independent onboard experience to explain data consumption and location services usage. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586412] Re: Remote scopes are very often empty
Ok, I've a suspiction it's a backend problem on the server; executing
the offending search query with the browser I get this:
{"departments": {"canned_query":
"scope://com.canonical.scopes.sevendigital", "subdepartments":
[{"canned_query":
"scope://com.canonical.scopes.sevendigital?dep=newreleases",
"has_subdepartments": false, "label": "New releases"}, {"canned_query":
"scope://com.canonical.scopes.sevendigital?dep=topalbums",
"has_subdepartments": false, "label": "Top albums"}, {"canned_query":
"scope://com.canonical.scopes.sevendigital?dep=toptracks",
"has_subdepartments": false, "label": "Top tracks"}, {"canned_query":
"scope://com.canonical.scopes.sevendigital?dep=genres",
"has_subdepartments": true, "label": "Genres"}], "label": "All
categories"}}
And it ends here, missing actual search results.
--
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/1586412
Title:
Remote scopes are very often empty
Status in Ubuntu Rest Scopes:
New
Status in unity-scopes-api package in Ubuntu:
New
Bug description:
I noticed that very often some remote scopes are empty (7digital,
EBay, Reddit..., but not Wikipedia - that one seems to be working
fine). When this happens, /home/phablet/.cache/upstart/smart-scopes-
proxy.log has the following errors:
[2016-05-27 16:18:25.326] INFO: SSRegistry: SmartScope: created query for
"com.canonical.scopes.sevendigital": ""
[2016-05-27 16:18:25.327] INFO: SSRegistry: SmartScopesClient.search(): GET
https://dash.ubuntu.com/smartscopes/v2/sevendigital/search?q=_id=486bd3e1-eba6-4316-8b77-2988c9002699_id=0=phone=en_GB=300
[2016-05-27 16:18:25.328] INFO: SSRegistry: User agent:
release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq
[2016-05-27 16:18:25.540] ERROR: SSRegistry: SmartScopesClient.search():
Failed to parse line: unity::ResourceException: Failed to parse json string: *
Line 1, Column 1
Syntax error: value, object or array expected.
[2016-05-27 16:18:25.540] INFO: SSRegistry: SmartScope: query for
"com.canonical.scopes.sevendigital": "" complete
[2016-05-27 16:21:17.337] INFO: SSRegistry: SmartScope: created query for
"com.canonical.scopes.ebay": ""
[2016-05-27 16:21:17.338] INFO: SSRegistry: SmartScopesClient.search(): GET
https://dash.ubuntu.com/smartscopes/v2/ebay/search?q=_id=08e1d6cb-fe8d-44a2-9105-4fa5d7420dc4_id=0=phone=en_GB=300
[2016-05-27 16:21:17.339] INFO: SSRegistry: User agent:
release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq
[2016-05-27 16:21:18.309] ERROR: SSRegistry: SmartScopesClient.search():
Failed to parse line: unity::ResourceException: Failed to parse json string: *
Line 1, Column 1
Syntax error: value, object or array expected.
Interestingly, I saw it once for Amazon even when it worked:
[2016-05-27 16:20:03.632] INFO: SSRegistry: SmartScope: created query for
"com.canonical.scopes.amazon": ""
[2016-05-27 16:20:03.634] INFO: SSRegistry: SmartScopesClient.search(): GET
https://dash.ubuntu.com/smartscopes/v2/amazon/search?q=_id=e0f83bae-8097-4b6f-8e00-42d9f969254c_id=0=phone=en_GB=300
[2016-05-27 16:20:03.634] INFO: SSRegistry: User agent:
release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq
[2016-05-27 16:20:04.695] ERROR: SSRegistry: SmartScopesClient.search():
Failed to parse line: unity::ResourceException: Failed to parse json string: *
Line 1, Column 1
Syntax error: value, object or array expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1586412/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586412] [NEW] Remote scopes are very often empty
Public bug reported: I noticed that very often some remote scopes are empty (7digital, EBay, Reddit..., but not Wikipedia - that one seems to be working fine). When this happens, /home/phablet/.cache/upstart/smart-scopes-proxy.log has the following errors: [2016-05-27 16:18:25.326] INFO: SSRegistry: SmartScope: created query for "com.canonical.scopes.sevendigital": "" [2016-05-27 16:18:25.327] INFO: SSRegistry: SmartScopesClient.search(): GET https://dash.ubuntu.com/smartscopes/v2/sevendigital/search?q=_id=486bd3e1-eba6-4316-8b77-2988c9002699_id=0=phone=en_GB=300 [2016-05-27 16:18:25.328] INFO: SSRegistry: User agent: release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq [2016-05-27 16:18:25.540] ERROR: SSRegistry: SmartScopesClient.search(): Failed to parse line: unity::ResourceException: Failed to parse json string: * Line 1, Column 1 Syntax error: value, object or array expected. [2016-05-27 16:18:25.540] INFO: SSRegistry: SmartScope: query for "com.canonical.scopes.sevendigital": "" complete [2016-05-27 16:21:17.337] INFO: SSRegistry: SmartScope: created query for "com.canonical.scopes.ebay": "" [2016-05-27 16:21:17.338] INFO: SSRegistry: SmartScopesClient.search(): GET https://dash.ubuntu.com/smartscopes/v2/ebay/search?q=_id=08e1d6cb-fe8d-44a2-9105-4fa5d7420dc4_id=0=phone=en_GB=300 [2016-05-27 16:21:17.339] INFO: SSRegistry: User agent: release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq [2016-05-27 16:21:18.309] ERROR: SSRegistry: SmartScopesClient.search(): Failed to parse line: unity::ResourceException: Failed to parse json string: * Line 1, Column 1 Syntax error: value, object or array expected. Interestingly, I saw it once for Amazon even when it worked: [2016-05-27 16:20:03.632] INFO: SSRegistry: SmartScope: created query for "com.canonical.scopes.amazon": "" [2016-05-27 16:20:03.634] INFO: SSRegistry: SmartScopesClient.search(): GET https://dash.ubuntu.com/smartscopes/v2/amazon/search?q=_id=e0f83bae-8097-4b6f-8e00-42d9f969254c_id=0=phone=en_GB=300 [2016-05-27 16:20:03.634] INFO: SSRegistry: User agent: release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq [2016-05-27 16:20:04.695] ERROR: SSRegistry: SmartScopesClient.search(): Failed to parse line: unity::ResourceException: Failed to parse json string: * Line 1, Column 1 Syntax error: value, object or array expected. ** Affects: ubuntu-rest-scopes Importance: Undecided Status: New ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-rest-scopes 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/1586412 Title: Remote scopes are very often empty Status in Ubuntu Rest Scopes: New Status in unity-scopes-api package in Ubuntu: New Bug description: I noticed that very often some remote scopes are empty (7digital, EBay, Reddit..., but not Wikipedia - that one seems to be working fine). When this happens, /home/phablet/.cache/upstart/smart-scopes- proxy.log has the following errors: [2016-05-27 16:18:25.326] INFO: SSRegistry: SmartScope: created query for "com.canonical.scopes.sevendigital": "" [2016-05-27 16:18:25.327] INFO: SSRegistry: SmartScopesClient.search(): GET https://dash.ubuntu.com/smartscopes/v2/sevendigital/search?q=_id=486bd3e1-eba6-4316-8b77-2988c9002699_id=0=phone=en_GB=300 [2016-05-27 16:18:25.328] INFO: SSRegistry: User agent: release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq [2016-05-27 16:18:25.540] ERROR: SSRegistry: SmartScopesClient.search(): Failed to parse line: unity::ResourceException: Failed to parse json string: * Line 1, Column 1 Syntax error: value, object or array expected. [2016-05-27 16:18:25.540] INFO: SSRegistry: SmartScope: query for "com.canonical.scopes.sevendigital": "" complete [2016-05-27 16:21:17.337] INFO: SSRegistry: SmartScope: created query for "com.canonical.scopes.ebay": "" [2016-05-27 16:21:17.338] INFO: SSRegistry: SmartScopesClient.search(): GET https://dash.ubuntu.com/smartscopes/v2/ebay/search?q=_id=08e1d6cb-fe8d-44a2-9105-4fa5d7420dc4_id=0=phone=en_GB=300 [2016-05-27 16:21:17.339] INFO: SSRegistry: User agent: release=15.04=1.0.6+15.04.20160520.3-0ubuntu1=0.5.7+15.04.20160523-0ubuntu1=8.12+15.04.20160520.1-0ubuntu1=344=bq [2016-05-27 16:21:18.309] ERROR: SSRegistry: SmartScopesClient.search(): Failed to parse line: unity::ResourceException: Failed to parse json string: * Line 1, Column 1 Syntax error: value, object or array expected. Interestingly, I saw it once for Amazon even when it worked: [2016-05-27 16:20:03.632]
[Touch-packages] [Bug 1585654] [NEW] surfacing_cache put in .local/share/unity-scopes/unconfined/SSRegistry
Public bug reported: While testing remote scopes on the phone today I noticed a fresh .surfacing_cache file created in the .local/share/unity- scopes/unconfined/SSRegistry directory. Looking at the contents it contains the data from a remote scope I used *last* (it gets overwritten each time I switch to a different remote scope). SmartScope.cpp code doesn't currently push surfacing results (it could be a nice idea to do that if we get server error?), so creating that file and overwriting it each and every time another remote scope is opened is wasteful. We should either disable this functionality completely for remote scopes or store unique file for every remote scope. ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Description changed: While testing remote scopes on the phone today I noticed a fresh .surfacing_cache file created in the .local/share/unity- scopes/unconfined/SSRegistry directory. Looking at the contents it contains the data from a remote scope I used *last* (it gets overwritten each time I switch to a different remote scope). SmartScope.cpp code doesn't currently push surfacing results (it could be a nice idea to do that if we get server error?), so creating that - file and overwriting it each time another remote scope is opened is - wasteful. We should either disable this functionality completely for - remote scopes or store unique file for every remote scope. + file and overwriting it each and every time another remote scope is + opened is wasteful. We should either disable this functionality + completely for remote scopes or store unique file for every remote + scope. -- 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/1585654 Title: surfacing_cache put in .local/share/unity-scopes/unconfined/SSRegistry Status in unity-scopes-api package in Ubuntu: New Bug description: While testing remote scopes on the phone today I noticed a fresh .surfacing_cache file created in the .local/share/unity- scopes/unconfined/SSRegistry directory. Looking at the contents it contains the data from a remote scope I used *last* (it gets overwritten each time I switch to a different remote scope). SmartScope.cpp code doesn't currently push surfacing results (it could be a nice idea to do that if we get server error?), so creating that file and overwriting it each and every time another remote scope is opened is wasteful. We should either disable this functionality completely for remote scopes or store unique file for every remote scope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1585654/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] Lag when favoriting/unfavoriting scopes via Manage Dash
Public bug reported: 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. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** 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 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: New Status in unity-scopes-shell package in Ubuntu: New 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 1583055] [NEW] Empty settings.ini created for every scope even if it doesn't have settings
Public bug reported: After recent changes to scope settings handling in shell plugin (the switch from QSettings to glib-based settings) we now get empty settings.ini and settings dir created for absolutely every scope in the system, even if it doesn't offer any settings. This doesn't pose any issues as far as I can tell (other than polluting fs), but it would be nice not to do that if not needed. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed ** 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 unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1583055 Title: Empty settings.ini created for every scope even if it doesn't have settings Status in Canonical System Image: New Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: After recent changes to scope settings handling in shell plugin (the switch from QSettings to glib-based settings) we now get empty settings.ini and settings dir created for absolutely every scope in the system, even if it doesn't offer any settings. This doesn't pose any issues as far as I can tell (other than polluting fs), but it would be nice not to do that if not needed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581495] Re: Crash when accessing a preview in the uapp explorer scope
** 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 unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1581495 Title: Crash when accessing a preview in the uapp explorer scope Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: When trying to access a preview in the uapp explorer scope it, unity8-dash crashes Backtrace: http://paste.ubuntu.com/16387928/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581495] Re: Crash when accessing a preview in the uapp explorer scope
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1581495 Title: Crash when accessing a preview in the uapp explorer scope Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: When trying to access a preview in the uapp explorer scope it, unity8-dash crashes Backtrace: http://paste.ubuntu.com/16387928/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581495] Re: Crash when accessing a preview in the uapp explorer scope
Opened a bug against the scope: https://github.com/bhdouglass /uappexplorer-scope/issues/6 -- 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/1581495 Title: Crash when accessing a preview in the uapp explorer scope Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: When trying to access a preview in the uapp explorer scope it, unity8-dash crashes Backtrace: http://paste.ubuntu.com/16387928/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581495] Re: Crash when accessing a preview in the uapp explorer scope
** Changed in: canonical-devices-system-image Status: New => Confirmed -- 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/1581495 Title: Crash when accessing a preview in the uapp explorer scope Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: When trying to access a preview in the uapp explorer scope it, unity8-dash crashes Backtrace: http://paste.ubuntu.com/16387928/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581495] Re: Crash when accessing a preview in the uapp explorer scope
Ok, the scope has a bug as it pushed two widgets with same ID on preview. Obviously we shouldn't crash, so that needs to be handled. Respective snipper of unity8-dash.log when this happens: --- Widget lookups dump "addReplaceWidget" --- Widget "header" at position 0 , lookup index 0 Widget "art" at position 1 , lookup index 1 Widget "types" at position 2 , lookup index 2 Widget "author" at position 3 , lookup index 3 Widget "hearts" at position 4 , lookup index 4 Widget "stars" at position 5 , lookup index 5 Widget "actions" at position 6 , lookup index 6 PreviewModel::addWidgetToColumnModel(): processing widget "author" PreviewModel::addWidgetToColumnModel(): destination for widget "author" is row 7 , column 0 PreviewWidgetModel::moveWidget(): invalid destRow 7 The offending widgets are authorWidget and moreWidget in this code, both with "author" id: https://github.com/bhdouglass/uappexplorer- scope/blob/master/src/uappexplorer-scope.go -- 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/1581495 Title: Crash when accessing a preview in the uapp explorer scope Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: When trying to access a preview in the uapp explorer scope it, unity8-dash crashes Backtrace: http://paste.ubuntu.com/16387928/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575744] Re: Language in the Store scope doesn't always change when user switches lang of the phone
Hi Lorn, added to the bug description. ** Description changed: Switching from English to Polish works as expected But then going back to English leaves me with store in Polish This survives reboots. + + Steps to reproduce: + 1. Go to Ubuntu Store scope (with your current language). + 2. Go to phone settings, change the language, accept & reboot the phone. + 3. Go to Ubuntu Store scope. Note how scope title and some strings such as "installed" changed for the new language (since these are provided locally by the scope for current LANG), but strings such as 'Highlight of the week' or departments names (hit the search lens icon to reveal departments) which come from the store still use the old language. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1575744 Title: Language in the Store scope doesn't always change when user switches lang of the phone Status in Canonical System Image: Confirmed Status in qtbase-opensource-src package in Ubuntu: New Status in unity-scope-click package in Ubuntu: In Progress Bug description: Switching from English to Polish works as expected But then going back to English leaves me with store in Polish This survives reboots. Steps to reproduce: 1. Go to Ubuntu Store scope (with your current language). 2. Go to phone settings, change the language, accept & reboot the phone. 3. Go to Ubuntu Store scope. Note how scope title and some strings such as "installed" changed for the new language (since these are provided locally by the scope for current LANG), but strings such as 'Highlight of the week' or departments names (hit the search lens icon to reveal departments) which come from the store still use the old language. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559596] Re: arale capacitive button not disabled on music playback
** Changed in: unity-scope-mediascanner (Ubuntu) Status: New => Invalid ** Changed in: unity-scopes-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1559596 Title: arale capacitive button not disabled on music playback Status in media-hub package in Ubuntu: Incomplete Status in mediaplayer-app package in Ubuntu: New Status in unity-scope-mediascanner package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: Arale ( Meizu MX4) When playing music either from music player or my music scope the capacitive button doesn't deactivate on Locked screen as usual. Usually it deactivates but on music playback it doesn't. This bug is since OTA8 days afaik currently on rc-proposed r276 and it's still there if any more of the information is needed i can gladly help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1559596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580074] [NEW] Please add timestamps to unity8-dash.log
Public bug reported: It would be super useful to have timestamps in unity8-dash.log, it's very helpful to be able to correlate events from dash log and other logs, such as scope-registry.log. I think unity-scopes-shell plugin is not the right place to install custom log handler, so opening it against unity8. ** 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/1580074 Title: Please add timestamps to unity8-dash.log Status in unity8 package in Ubuntu: New Bug description: It would be super useful to have timestamps in unity8-dash.log, it's very helpful to be able to correlate events from dash log and other logs, such as scope-registry.log. I think unity-scopes-shell plugin is not the right place to install custom log handler, so opening it against unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1580074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542854] Re: App installation failure uses subtitle for a potentially long label
** Branch linked: lp:~stolowski/unity-scope-click/fix-1542854 -- 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/1542854 Title: App installation failure uses subtitle for a potentially long label Status in Canonical System Image: Confirmed Status in unity-scope-click package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Won't Fix Bug description: See this image: http://i.imgur.com/BFzgwnb.png The error messages is elided while it should be wrapped. In order to reproduce the above message, you can fill up the home folder to only have a few MB left and then try to install the document viewer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542854] Re: App installation failure uses subtitle for a potentially long label
** Changed in: unity-scope-click (Ubuntu) Status: Confirmed => In Progress -- 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/1542854 Title: App installation failure uses subtitle for a potentially long label Status in Canonical System Image: Confirmed Status in unity-scope-click package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Won't Fix Bug description: See this image: http://i.imgur.com/BFzgwnb.png The error messages is elided while it should be wrapped. In order to reproduce the above message, you can fill up the home folder to only have a few MB left and then try to install the document viewer. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502282] Re: "unknown" connectivity status problematic
Michi, your guess was correct, the shell doesn't set connectivity status in ActionMetadata. Attached branch fixes that. ** Branch linked: lp:~stolowski/unity-scopes-shell/set-connectivity- status-of-actionmetadata -- 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/1502282 Title: "unknown" connectivity status problematic Status in The Savilerow project: New Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: metadata provides a scope a network connectivity status enum with three possible states: * connected * disconnected * unknown Sometimes unknown is the current state. This is quite problematic because in general a scopes that queries the network (that is, most scopes) need to know whether there is network or is not network and depending on this either make the network queries or display an error message. A status of unknown connectivity leaves the scope with no valid option: * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily * the scope could assume the network is up, but this is dangerous if it is not up To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459260] Re: Settings screen uses the word "Display" 15 times
What is the desired solution from design pov?
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
** Changed in: unity-scopes-shell (Ubuntu)
Importance: Undecided => Medium
--
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/1459260
Title:
Settings screen uses the word "Display" 15 times
Status in Ubuntu UX:
New
Status in unity-scopes-shell package in Ubuntu:
Confirmed
Bug description:
Ubuntu 15.04 r6
1. Go to the Today scope.
2. Tap the Settings button.
What you see: The settings screen uses the word "Display" 15 times.
What you should see: The screen uses the word "Display" either once
("Display:" as an intro label), or not at all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1459260/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537112] Re: Preview widgets may not get displayed if scope makes a mistake in layout definition
** Branch linked: lp:~stolowski/unity-scopes-shell/preview-updates ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (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/1537112 Title: Preview widgets may not get displayed if scope makes a mistake in layout definition Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: From a quick look at PreviewModel::addWidgetToColumnModel method it seems like the implementation is prone to errors in column layout definitions: if scope pushes more widgets than defined in the layout, they are likely to be ignored and not inserted into the widget model. I think the proper strategy would be to append them at the bottom of the first column. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1537112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1545866] Re: First scope results only load after unlock
@Pat yes, we do already prepopulate next two scopes following currently active scope; this takes affect after unlocking though. With this branch we will prepolute the first scope even when locked and as soon as you unlock, the next two will be prepopulated too. -- 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/1545866 Title: First scope results only load after unlock Status in Canonical System Image: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Results in the first scope only load after you unlock the device instead of being already there when you unlock. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.11+15.04.20160212-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Feb 15 22:58:19 2016 InstallationDate: Installed on 2016-02-13 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160213-020304) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378186] Re: When the only app of a selected department is uninstalled, the empty department remains selected
It's still the case. I don't think the shell should implement any logic for such cases. Click scope could check if the department becomes empty after uninstall step and - if so - return the ActivationResponse with a CannedQuery that requests the root department. ** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => 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/1378186 Title: When the only app of a selected department is uninstalled, the empty department remains selected Status in unity-scope-click package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: I found this on on krillin #87 while testing silo 18 with unity-plugin-scopes 0.5.4+14.10.20141002.1-0ubuntu1 http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm=landing-018 I haven't tested it without the silo. Steps to reproduce: Install an app that will add a new department to the list of installed apps. I installed 2ubuntu. Go back to the home. Select the newly added department. In my case, Books & Comics. Long press on the newly installed app. Uninstall it. The dash is refreshed and the app disappears, but the empty department remains selected. See the attachment. I think that if the dash is refreshed and the selected department is empty, we should be back to All the apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1378186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547429] Re: Copy/Paste within scope
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Importance: Undecided => Wishlist -- 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/1547429 Title: Copy/Paste within scope Status in Canonical System Image: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Texts from scopes should be selectable and can be copied and pasted to other apps. Scopes present information to the user and it would be good if the user can use the information on other apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423535] Re: Search doesn't work for photos scope for images on internal stograge
Pictures are discovered by mediascanner2 service and photos scope. This bug report is very old, please verify if it's still the case - marking it incomplete for now in these projects and marking invalid for unity- scopes-shell. ** Also affects: photos-scope Importance: Undecided Status: New ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: photos-scope Status: New => Incomplete ** Also affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Changed in: mediascanner2 (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/1423535 Title: Search doesn't work for photos scope for images on internal stograge Status in Photos Scope: Incomplete Status in mediascanner2 package in Ubuntu: Incomplete Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: Steps To reproduce: 1. Copy some image files on device under /phablet/home/Pictures and remember the file names 2. Navigate to Photos scope 3. Search for the image name copied on internal storage Observe that search doesn't return the result for internal storage. To manage notifications about this bug go to: https://bugs.launchpad.net/photos-scope/+bug/1423535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470697] Re: Incorrectly sized requests for album art
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1470697 Title: Incorrectly sized requests for album art Status in unity-scope-mediascanner package in Ubuntu: Triaged Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: Go to the My Music scope and tap on Artists. In the artists view, tap on one of the albums. At that point, the thumbnailer gets the following request: thumbnailer-service: [02:59:04.731] "album: Pink Floyd/The Dark Side Of The Moon [2011 - Remaster] (2304,0): 0.129131 sec (FULL-SIZE HIT)" 2304 is bigger than the entire screen, and the thumbnailer will delivers the largest size it can (limited to 1920). But the actual thumbnail that's displayed looks like it's about 250-300 pixels wide. It would be easier on the battery and on cache storage if the request would be issued at the correct size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1470697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429214] Re: [Scopes] Departments not behaving consistently when navigating too/from a Scope
This ("Entering a search query should not clear the selected
'department' but instead, it should norrow down the results within that
specific department") has been fixed as part of OTA10 with introduction
of filters and search semantics changes. Closing.
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => Fix Released
--
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/1429214
Title:
[Scopes] Departments not behaving consistently when navigating
too/from a Scope
Status in Ubuntu UX:
Fix Committed
Status in unity-scopes-shell package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu:
Invalid
Bug description:
Departments are currently not cleared for Apps (as well as other Scopes) when
navigating away/too a Scope. However, if a user selects a department and then
conducts a search, navigating away/too the scope clears the search AND resets
the department (tested in the Amazon and Ebay Scopes).
Additionally, opening the department drop-down shows the previously selected
department as still being active/applied.
Recommendation:
Apps Scope is a special case where we should clear searches and reset
departments (including within the department drop-dow) when a user navigates
away from the scope.
All other scopes should preserve both the department and (where
relevant) filters, but clear searches (which are easily accessible by
beginning a new search and selecting from the recent search list).
--- UX Comment ---
Entering a search query should not clear the selected 'department' but
instead, it should norrow down the results within that specific
department. I understand that this was specified by design before,
however, that's not the behaviour that we want to mantain in the
future version of scopes. This behaviour is not specific to a single
scope but the default case for all of them.
For further information please refer to design spec:
https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit#
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1429214/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568544] Re: Scopes are smoothest with no microSD card
Do you have a lot of audio or video files on that SD card? The only explanation I can see is the card is scanned for media content by mediascanner service (mediascanner2 in launchpad; this probably happens every time you insert it). This can tax the CPU a lot if the card has a lot of files on it. In any case the problem is unrelated to unity-scopes-shell, so marking invalid in this project. ** Changed in: unity-scopes-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1568544 Title: Scopes are smoothest with no microSD card Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: I removed my microSD card for the first time on the day the OTA-10 update arrived. After the update, the scopes were smooth as silk and I thought this was as a result of the OTA. But after re-inserting the microSD card they are back to their normal way; smooth for a few minutes, jerky for a few minutes. Card: SanDisk 16GB Micro SD HC Scopes: Today, Apps, My Videos, Dictionary, Simon's Cat, Discerning Duck, Crafting, Command Line This is 100% reproducable on every ocassion now when I remove or insert the card and either symptom remains - ie, it's not something that just lasts a moment and then corrects itself. I have the Log Viewer app installed. I can upload any logs requested. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1568544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492252] Re: Allow direct linking to a Preview via uri
This poses a challenge, because shell needs to pass the complete copy of the activated result with preview request. When preview is requested by the user via the UI, the shell naturally has the result in question and can pass it. But to make this work via a canned query, we would need to serialize entire result in the canned query, so that the query can be invoked from any context of the UI. While this is doable, I think it will be very fragile and hard for apps to get right (even a subtle change in preview handling internals of the scope may break canned queries created for it by external apps). -- 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/1492252 Title: Allow direct linking to a Preview via uri Status in unity-scopes-api package in Ubuntu: Invalid 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/ubuntu/+source/unity-scopes-api/+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 1492252] Re: Allow direct linking to a Preview via uri
** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1492252 Title: Allow direct linking to a Preview via uri Status in unity-scopes-api package in Ubuntu: Invalid 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/ubuntu/+source/unity-scopes-api/+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 1545866] Re: First scope results only load after unlock
** Branch linked: lp:~stolowski/unity-scopes-shell/prepopulate-scopes- when-locked -- 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/1545866 Title: First scope results only load after unlock Status in Canonical System Image: Triaged Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Results in the first scope only load after you unlock the device instead of being already there when you unlock. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.11+15.04.20160212-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Feb 15 22:58:19 2016 InstallationDate: Installed on 2016-02-13 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160213-020304) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1545866] Re: First scope results only load after unlock
** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1545866 Title: First scope results only load after unlock Status in Canonical System Image: Triaged Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Results in the first scope only load after you unlock the device instead of being already there when you unlock. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.11+15.04.20160212-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Feb 15 22:58:19 2016 InstallationDate: Installed on 2016-02-13 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160213-020304) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471914] Re: Scope search queries don't persist departments
This has been fixed with OTA10, closing. ** Changed in: unity-scopes-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1471914 Title: Scope search queries don't persist departments Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scope-snappy package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: I have a scope with departments A and B. A is the root department (id: ""), and B has id: "b". Scenario: 1) Initially surface scope, A is the current department. 2) Switch to the B department. 3) Run search query, typing very slowing so as to cause multiple searches to be run while the query is being typed. Expected results: Search results from each search during the typing of the search query should be limited to department B. Actual results: Only the results from the very first search is from department B. As soon as the second (and subsequent) searches occur while typing, the search results are from the root department (A). Suspected reason: Adding debug prints to the scope shows that the department for the search query is only passed along for the first search. If the search is modified or being typed slowly enough so as to cause multiple searches to occur, subsequent queries don't include the department at all, thus the scope defaults to the root department. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1471914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485887] Re: ClickStore preview refreshes completely when pressing Install or the installation finishes
** Branch linked: lp:~stolowski/unity-scopes-shell/preview-updates ** Branch linked: lp:~aacid/unity8/previewActionsModelChange ** Changed in: unity8 (Ubuntu) Status: Invalid => In Progress ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) -- 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/1485887 Title: ClickStore preview refreshes completely when pressing Install or the installation finishes Status in unity-scope-click: New Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Right now, when you install an app, the complete screen refreshes when you press the install button. The same when the installation completes and the progress bar becomes a button again. It should only update the button instead of destroying and recreating the whole model. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-click/+bug/1485887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568035] Re: cannot change department from code
Do we have any idea how many services could be limited that way (and how many scopes are potentially affected)? It would be relatively easy to add to the departments API, but this will lead to inconsistencies between scopes. Need design input. -- 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/1568035 Title: cannot change department from code Status in canonical-scopes-project: New Status in Ubuntu UX: New Status in unity-scopes-api package in Ubuntu: New Bug description: There is no ability to change the current department from code. This means that the scope cannot "do the right thing" when a user enters a query string in some cases. For example, suppose a scope has departments that represent a web api's departments. And suppose the web api does not support searching inside a department but only supports searches over the whole site. What is the scope developer to do when the user is in a department *and* they enter a query string? Because there is no way now to change the department (perhaps to a department named "Search Results"), the dev *must* return results in the current department, which is incorrect. 500px web api and our 500px scope is like this. 500px has "streams" like "Editors", "Fresh today" etc. The scope displays these as departments. However, the 500px web api has no api to provide search results limited to a stream. Therefore when a user is in a department, for example "Fresh Today" and they enter a search string, the results are in fact not limited to Fresh Today but they are displayed in the Fresh Today department, which is not correct. It is possible (and the proposed the 1.0 version of the 500px scope does this) to avoid the problem by applying the search query string to the department's results. So for example if the search was "strawberry" and the user was in "Fresh Today" department, the scope only displays received "Fresh Today" results that contain "strawberry". But this is sub-optimal because the scope needs to keep querying the api to get more and Fresh Today results trying to find matches, which takes time and may not find a match. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-scopes-project/+bug/1568035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568007] Re: The main app scope doesn't show up
If this problem happens again, please attach the following log files: /home/phablet/.cache/upstart/unity8-dash.log /home/phablet/.cache/upstart/scope-registry.log -- 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/1568007 Title: The main app scope doesn't show up Status in Canonical System Image: New Status in unity-scopes-api package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I upload a picture that explains the bug better than me. The apps from the phone doesn't show up in the app scope. After OTA-10 update it happens 2 times. I had to reboot and after that everything was ok. After OTA-10 update I needed to reboot the phone too many times. I don't like this update. It's beautifull as design and many bugs were solved with this update, but many things are slowing down the phone maybe. If you need more info I can search for logs with adb if you can give me more instructions. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1568007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567429] Re: Scope::settings() is too slow
>From a quick look the problem is most likely caused by Scope::settings() getter, which calls update_child_scopes() every time settings model is accessed by the getter, and this involves IPC with m_scopeProxy->child_scopes() call, which is a blocking call. ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1567429 Title: Scope::settings() is too slow Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: Evaluating settingsEnabled: scopeView.scope && scopeView.scope.settings && scopeView.scope.settings.count > 0 || false in GenericScopeView.qml takes around 300 ms when running on the phone, which basically feels like an eternity if you're trying to use the phone to scroll, change to another scope, etc If this needs heavy calculation this should be either pre-calculated and cached or calculated in a separate thread and then signalled with a signal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1567429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566952] [NEW] Push method for filters should be updated
Public bug reported: The push(filters, filterState) method should be marked deprecated. The doc for this method should be updated to say it's only useful for the UI or for clients (aggregator scopes) and sending modified filterState back to the UI has no effect. A new overloaded push method that only takes filters should be added. ** 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/1566952 Title: Push method for filters should be updated Status in unity-scopes-api package in Ubuntu: New Bug description: The push(filters, filterState) method should be marked deprecated. The doc for this method should be updated to say it's only useful for the UI or for clients (aggregator scopes) and sending modified filterState back to the UI has no effect. A new overloaded push method that only takes filters should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1566952/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Branch linked: lp:~stolowski/unity-scopes-shell/invalid-locale- crashfix -- 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: Confirmed 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 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
And a new bug just reported by Michi against GCC with a minimal test case: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70493 -- 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: Confirmed 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 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
After trying to come up with a fallback for wrong locale I've to say
this cannot be fixed at the point we hit the problem in unity-scopes-
shell. It's already too late, and moreover there seem to be issues with
the libstdc++ library when locale setup is broken and it's impossible to
recover.
Related to this:
http://stackoverflow.com/questions/1745045/stdlocale-breakage-on-macos-10-6-with-lang-en-us-utf-8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15467
When the locale setup is broken (which I can easily reproduce in my VM with
only minimal ubuntu system with some locale settings pointing to non-existing
PL locales, and LC_ALL is unset), all the locale-related C++ functions throw
when trying to get current locale name and they also throw after trying to set
LC_ALL to "C" at this point. In summary, these method calls throw:
std::locale("") (should get us current locale setup)
std::setlocale(LC_ALL, "C")
std::locale::global(std::locale::classic())
The only workaround I can think of is to avoid the crash, end up with a blank
Dash page and log an error message to unity8-dash.log.
For the occasional problem with the tests we see when landing the package, I'll
make sure LC_ALL=C when tests are executed.
** Bug watch added: GCC Bugzilla #15467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15467
** Bug watch added: GCC Bugzilla #70493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70493
--
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:
Confirmed
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 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale
Ok, after discussing it on the standup we agreed that unity-scopes-shell should handle this exception and fallback to standard locale if the two conditions hold true: - scopes api runtime initialization throws and - current locale is not "" or "C" already ** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => High ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (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/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: Confirmed 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 1485887] Re: ClickStore preview refreshes completely when pressing Install or the installation finishes
I'm working on changes to preview models in unity-shell-plugin to avoid clearing of the model and updating it instead with new preview data. The change will be transparent to scopes and unity8. -- 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/1485887 Title: ClickStore preview refreshes completely when pressing Install or the installation finishes Status in unity-scope-click: New Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Right now, when you install an app, the complete screen refreshes when you press the install button. The same when the installation completes and the progress bar becomes a button again. It should only update the button instead of destroying and recreating the whole model. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-click/+bug/1485887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
