** Changed in: snapd (Ubuntu)
Status: Fix Released => In Progress
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Luna what was the fix, can you link to the respective change? I'm still
seeing the problem with up-to-date 21.04 (and there were no updates
reported for zfs-linux; was it actually released)?
The tentative fix for snapd hasn't been commited yet in snapd; if the
problem was fixed elsewhere then we
@Christopher as far as I understand the fix happened in ubiquity
installer, so it will only take effect on fresh installation (which is
fine given that this is during beta). See the comments under
https://github.com/snapcore/snapd/pull/10113
--
You received this bug notification because you are a
I don't think we want (or can) change HOME in snapd (due to undesired
consequences and breaking many snaps), it works as designed, i.e. gives
snaps dedicated areas where they can freely write data to, including
hidden files; access to real user $HOME may not even be allowed unless
home interface is
I've check this with Chipaca, there is no plan to change anything in
snapd wrt this bug on the following basis: (a) user can look at the
channel map to know what's in stable, and (b) store can change what's
returned outside the channel map, which snapd will forward on.
** Changed in: snapd
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724316
Title:
"Sorry, something went wrong cannot authenticate to snap store ..."
w
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Status: In Progress => Fix Committed
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671421
Title:
Snap apps keep asking installing ubuntu-app-platform and connecting
p
** Changed in: snapd
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742637
Title:
GNOME Software and snapcraft.io present developer identity differently
To man
Public bug reported:
After the installation completes, fontconfig cache files
(/var/cache/fontconfig) should be copied from the live CD session to the
just installed system, before reboot.
The rationale:
Snapd creates fontconfig cache files (/var/cache/fontconfig) for
fontconfig cache format v6
** Changed in: snapd
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824162
Title:
/usr/lib/snapd/snapd
I think the bug is in the go-udev package (upstream). The Monitor()
function returns a 'quit' channel that the caller uses to stop
processing. Monitor() runs a backgroud goroutine that monitors/reads
from netlink socket and stops if quit channel is written to. I think the
problem is that the quit c
The bug may occur regardless of experimental hotplug flag, and may
prevent clean shutdown of snapd - of course only if there is udev
netlink activity, therefore setting to critical.
** Changed in: snapd
Importance: High => Critical
** Changed in: snapd (Ubuntu)
Importance: Medium => Critica
My initial conclusion about go-udev being the culprit was premature, the
socket closing & quit channel code looks fine after all, the problem
lies somewhere else and may be something in the go runtime stack and
it's very unclear for the time being.
** Changed in: snapd (Ubuntu)
Importance: Crit
I suspect you've been able to resolve this, sorry we never got back to
you about it.
I'm closing it as "Won't fix", because we didn't do anything about this,
but if you're still stuck there's probably a cause for this that isn't
necessarily snapd itself and we can probably figure it out.
Again, s
*** This bug is a duplicate of bug 1781513 ***
https://bugs.launchpad.net/bugs/1781513
** This bug has been marked a duplicate of bug 1781513
package snapd 2.32.9+18.04 failed to install/upgrade: installed snapd
package post-installation script subprocess was killed by signal (Terminated)
Is is still an issue? Given that this report is very old I suspect the
problem was resolved, therefore I'm setting to 'incomplete'. Please
respond if you think it is still the case.
** Changed in: snapd
Status: New => Incomplete
** Changed in: snapd (Ubuntu)
Status: New => Incomplet
I suspect you've been able to resolve this, sorry we never got back to
you about it.
I'm closing it as "Won't fix", because we didn't do anything about this,
but if you're still stuck there's probably a cause for this that isn't
necessarily snapd itself and we can probably figure it out.
Again, s
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781447
Title:
snapd not updated or deleted
To manage notifications about this bug go to
Do you have any apparmor denials in the system log when you observe this
slowdown? (run journalctl, look for 'apparmor=DENIED'?
(for what it is worth chromium snap starts just fine for me on fresh
18.04 and 19.10 systems, but I reckon NFS may be a key here, and I don't
have it).
--
You received
Please do not spam this bug report with meaningless comments. Comments under
bug reports should be limited to the merit and provide extra info where info is
lacking, "me too" is not really bringing anything to the discussion.
It is understood that this issue is very important for some users. Zyg
I had a quick look and it seems that UpdateWithDeviceContext can append
"snap-switch-channel" to taskset from doUpdate(), which means a task
gets scheduled after "check-rerefresh" (which panics if it finds any
tasks waiting for it). AFAIR "check-rerefresh" was meant to be the last
in the change.
-
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682023
Title:
snapd/snap-confine leaves behind /etc/apparmor.d/usr.lib.snapd.snap-
c
I'm tentatively adding systemd/dpkg.
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Also, the list of installed snaps may be relevant in understanding what
happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868706
Title:
Snapd postinst script hangs
To manage notifications abo
@Mark does 'snap changes' (and then 'snap change ' if you see any
failed changes) reveal antyhing interesing? Some of the older focal
images had broken seeds that would never succeed, potentially causing
other issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ok, reproduced with focal and broken seeds from an older image, symptoms
are exactly the same (including ps/pstree output). The problem is caused
by blocking on snapd.seeded.service (which waits for seeding to
complete, but it's never going to complete with broken seeds).
Given that this is an edg
*** This bug is a duplicate of bug 1841137 ***
https://bugs.launchpad.net/bugs/1841137
** This bug has been marked a duplicate of bug 1841137
/dev/loopX devices left around for removed snap revisions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Changed in: snapd
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669000
Title:
classic snap can't use confinement override
To manage notifications about this bug
** Changed in: snappy
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647517
Title:
Segmentation fault on core snap refresh from candidate channel
To manage notifica
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852635
Title:
mount-ns te
They did (e.g. data=ordered is gone), plus an entry for systemd is gone,
affecting lots of entries (indices changed by 1). I'm on it.
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member o
The changes are caused by kernel 5.0. PR:
https://github.com/snapcore/snapd/pull/7756
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
*** This bug is a duplicate of bug 1699768 ***
https://bugs.launchpad.net/bugs/1699768
Thanks for the report and I apologize for late reply... The problem was
reported by others as well and fixed long time ago, we just forgot to
update this one. Thank you!
** This bug has been marked a duplic
I understand this can be confusing, but I'm not sure snapd should be in
the business of warning about missing desktop components or dbus
services of the given interface.
Snapd's desktop interface, as other snapd interfaces, grants access to
dozens of resources/subsystems, some of which may not be
Perhaps it could go into browser-support interface? To be discussed on
the forum / with security team I think.
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: snapd
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901578
Title:
Cannot remove snap package ubuntu 20.10
To man
I'll work on a fix; as workaround it is also possible to use 'snap
remove --purge ' (which of course skips snapshot creation).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901578
Title:
Cannot rem
I investigated and reproduced this with:
$ snap install hello-world
$ mkdir /home/fakeuser/snap
$ chown -R 1090:1088 /home/fakeuser (use uid:gid that are not used on the
system).
$ snap remove hello-world
The problem is only affecting groovy and it appears to be fixed with
https://github.com/sna
I don't see anything related to snapd in the attached logs, the camera
plug is connected and there are no denials related to camera access in
the dmesg.txt (the other apparmor denials seem unrelated to camera
interface). I'm closing this in snapd; please re-open if needed.
** Changed in: snapd
Could you please provide system log (from journalctl) and output of
'snap changes'? If there is any change with error status, the please
also attach the output of 'snap change ' (ID is the id of the change
in error). Thank you
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You
Thanks for reporting, reproduced, the problem is indeed strictly ZFS-
related and appears to be related to a number of zfs-related services
and mount units that need to be ready before mount units for snaps can
be executed during boot, otherwise snap blobs under
/var/lib/snapd/snaps/* cannot be acc
A tentative workaround for snapd discussed above:
https://github.com/snapcore/snapd/pull/10113
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922293
Title:
Snaps appear broken on 21.04 Beta with ZFS
@Colin After=.. only defines ordering but it's a loose coupling and has
no effect is the service doesn't exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922293
Title:
Snaps appear broken on 21
Thanks for providing a test snap; unfortunately it wouldn't build for me
(I won't provide more details about build error since I don't want to
derail/confuse the discussion), but I've quickly built a similar snap
that doesn't need java and simply touches given path under home, and it
worked fine wi
*** This bug is a duplicate of bug 1884849 ***
https://bugs.launchpad.net/bugs/1884849
** This bug has been marked a duplicate of bug 1884849
Error message trying to refresh or uninstalling a snap ( gimp )
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
One task actually is in error (it just results in undoing of the entire
change) - lxd install hook.
And this is the culprit:
Run install hook of "lxd" snap if present
2020-06-02T15:15:59Z ERROR run hook "install": /usr/lib/snapd/snap-
confine: error while loading shared libraries: libpthread.so.
It seems to be ipv6-related but I'm not using ipv6 so couldn't verify.
FWTW I played with chromium snap on focal with ipv4 and couldn't spot
any DNS lookup slowness, it was super fast. I've updated the title of
the bug report accordingly.
** Summary changed:
- chromium snap from focal fails DNS l
Is this still the case with current focal, or did the issue go away
after following Jamie's suggestions?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864125
Title:
certain services fail to start after removing snapd
To manage notifications
The problem is still affecting current Cosmic image (from 11th of June)
and has been reported on the https://forum.snapcraft.io/t/gnome-
calculator-failed-to-create-symbolic-link/5742/22 ; any reason the re-
order seed.yaml hasn't landed?
--
You received this bug notification because you are a me
See the first error reported by apt-get:
"Cannot start click due to a conflict with a different locally-installed
Python 'click' package. Remove it using Python packaging tools and try
again."
It seems there is a conflict between a locally installed 'click' python
package and the click machinery
I think the cause of this problem are filters, they are apparently not
reset correctly in this scenario. If you expand the filters on the 2nd
search and select Applications, it works as a workaround too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
1. Go to Manage Dash. Make sure you have a few scopes favorited.
2. Long press to start the "edit mode". Move the 2nd scope on the fav list to
the last position in favs
3. Leave "edit mode" by pressing the big X button in Manage Dash view.
4. Unfavorite the last scope by tapp
*** This bug is a duplicate of bug 1587448 ***
https://bugs.launchpad.net/bugs/1587448
** This bug has been marked a duplicate of bug 1587448
Can't reboot device from snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Changed in: snappy
Status: Fix Committed => Fix Released
** Changed in: snapd (Ubuntu Yakkety)
Status: Triaged => Fix Released
** Changed in: snapd (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bu
This has been fixed last month, and is available in the current release
in xenial (snap remove --revision ...; see man snap). Also, a garbage-
collector was implemented to keep only one revision prior to current one
and remove older ones.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583687
Title:
Snap type is not validated
To manage notifications about this
** Description changed:
Use case:
System Settings uses this dbus api.
What happens:
“The name com.canonical.usensord was not provided by any .service files”
What should happen:
An interface should exist, giving System Settings access to the usensord dbus
API.
+
+ Note: this int
** Branch linked: lp:~stolowski/unity-scopes-shell/fix-bileto-hook-
script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611485
Title:
"snap revert" doesn't remove the reverted version
To manage n
** Branch linked: lp:~stolowski/unity-scopes-shell/fix-bileto-hook-
script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612460
Title:
[MIR] unity-scopes-shell
To manage notifications about this b
** Branch unlinked: lp:~stolowski/unity-scopes-shell/fix-bileto-hook-
script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611485
Title:
"snap revert" doesn't remove the reverted version
To manage
Hi Jean, thanks for reporting. This looks really weird, it's seems to be
a Go compiler problem. We haven't seen any issue like that in our builds
(and we re-build several times a day), neither on xenial nor yakkety
machines, so I don't really have any suggestion for that other than
reporting this a
Actually fixed with this PR: https://github.com/snapcore/snapd/pull/1868
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622045
Title:
/etc/systemd/system/multi-user.target.wants/snapd.* symlinks not
cleaned up
PR: https://github.com/snapcore/snapd/pull/1893
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: snapd (Ubuntu)
Status: Triaged => In Progress
--
You received
** Changed in: snapd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581791
Title:
package snapd 2.0.2 failed to install/upgrade: package snapd is not
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622045
Title:
/etc/systemd/system/multi-user.target.wants/snapd.* symlinks no
Hi Jonas. I couldn't find any documentation for this interface, I also
tried the following on krillin:
gdbus introspect --system --dest com.canonical.usensord --object-path
/com/canonical/usensord/haptic
but got:
Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
com.canonica
Hi Roberto. It's very probable that this problem was fixed, but with no
clear steps for reproducing it's hard to verify. Do you still have this
snap around and can re-try with the current version of snapd?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug no
Hi Sapan, thanks for reporting. This looks like a transient problem with
state of the packages in the system, is it still the case with up-to-
date system?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bug
It looks like for whatever reason systemd couldn't be reached at
org.freedesktop.systemd1 on package removal... I don't think snapd
package is guilty here. Did you see it again with subsequent updates of
snapd?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this b
Right. Just to clarify, the two new hooks are 'pre-refresh' and 'post-
refresh'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611638
Title:
snap upgrade hook
To manage notifications about this bu
Looks like it's related to the changes to settings model made from a
separate thread (QtConcurrent is used to update child scopes).
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => Confirmed
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson
Ok, I was able to reproduce the issue.
I've checked unity-scopes-shell plugin with a debug branch
(https://code.launchpad.net/~stolowski/unity-scopes-shell/debug-
category-link; packages available here https://code.launchpad.net
/~unity-api-team/+archive/ubuntu/dev-build-1/+packages) and it seems
Daniel, it seems that all bugs that end up in qFatal() fall into the
same bucket.. The error you linked
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
aborts because of Mir:
#4 QMessageLogger::fatal (this=0xb6410088 ,
this@entry=0xb6fa9000, msg=0xb4160e50 "UbuntuClient
Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
Traceback (most recent call last):
File "/usr/bin/click", line 55, in
from click import commands
ImportError: cannot import name 'commands'
[1mdpkg:[0m error processing package libunity-scopes1.0:amd64 (--configure):
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630845
Title:
unity8-dash crashed with SIGSEGV in
scopes_ng::UbuntuLocationS
Public bug reported:
Please update zmqpp to version 4.1.2 with the following patch that I proposed
upstream (it got merged into their "develop" branch):
https://github.com/zeromq/zmqpp/pull/167/files
(alternatively, use master + my patch or develop branch of zmqpp).
This will require the curren
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This also affects scopes, we get empty art for thumbnailers uri such as
image://thumbnailer/file:///snap/unity8-session/...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620635
Title:
libapparmor's
** Changed in: unity-scopes-api (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639249
Title:
Result art not displayed when run in a snap
To manage notifica
As discussed no change is needed on scopes api level. Scopes should be
using scope_directory() getter to get the base dir and then use all
assets paths relative to that; scope_directory() uses $SNAP prefix
already.
There is a problem though with thumbnailer uris, such as
image://thumbnailer/file:/
Here is the error returned by thumbnailer in the unity8-dash.log when
processing image://thumbnailer/file:/// uris:
[2016-11-08:16:59:24.600] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus
error: Handler::checkFinished(): no artwork for thumbnail:
/snap/unity8-session/x4/usr/lib/x86_64-linu
Please ignore my last comment about this affecting scopes... It was a
different root cause afterwards (missing mime database and gdk-pixbuf
loaders/cache - https://code.launchpad.net/~stolowski/unity8-session-
snap/thumbnailer-fixes/+merge/310756 should fix it).
--
You received this bug notificat
@Daniel I see your point about Mir. Anyway, all I'm saying is this
problem manifested via
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
is completely different from the original problem described in this bug.
The only common thing is qFatal() gets called. In the origina
*** This bug is a duplicate of bug 1655936 ***
https://bugs.launchpad.net/bugs/1655936
Marked this bug as duplicate of #1655936 to unconfuse errors.ubuntu.com
(even though the bugs are technically different issues and the one from
this bug was fixed long time ago).
** This bug has been marked
This has been fixed with commit 7745892bb0d4d8d1fc07d445974728d915f8dccd
on 2016-12-05.
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
The "Not connected..." message comes from unity8 code:
src/CachingNetworkManagerFactory.cpp
33:qDebug() << "Not connected to the internet. Request for" <<
request.url().toString() << "will be served only from the cache.";
So it seems that it (QNetworkManager?) thinks network is down.
--
>From the symptoms it seems that the list of favorited scopes got messed
up somehow. Did you uninstall unity-scope-click scope before at any
point?
This list can be (re)set with e.g.
$ gsettings set com.canonical.Unity.Dash favorite-scopes
"['scope://unity-scope-nearby', 'scope://clickscope']"`
** Changed in: unity-scopes-shell (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603186
Title:
Apps scope not shown in the dash (but is installed)
To ma
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: unity-scopes-shell (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: unity-scopes-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => In Progress
--
You received this bug not
** Branch linked: lp:~stolowski/unity-scopes-shell/favoriting-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603186
Title:
Apps scope not shown in the dash (but is installed)
To manage notifi
** Branch linked: lp:~stolowski/unity-scopes-shell/favoriting-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583067
Title:
Lag when favoriting/unfavoriting scopes via Manage Dash
To manage no
*** This bug is a duplicate of bug 1547573 ***
https://bugs.launchpad.net/bugs/1547573
Yes, both these issues are known and were documented (+ bugs opened) in
the test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/scopes
when the feature was implemented, both causes by issues outside of
Public bug reported:
This test fails pretty consistently only on arm64 in yakkety:
22: [ RUN ] SmartScopesClientTest.consecutive_searches
22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test:
SmartScopesClient.search(): GET
http://127.0.0.1:1024/demo/search?q=stuff&session_id=session
** Description changed:
This test fails pretty consistently only on arm64 in yakkety:
22: [ RUN ] SmartScopesClientTest.consecutive_searches
22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test:
SmartScopesClient.search(): GET
http://127.0.0.1:1024/demo/search?q=stuff&session
Looks like it's crashing on invalid locale setup (boost throws exception
on us); what is your locale (language) setup?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615614
Title:
dash is empty, sco
I agree this is a problem, it's an old bug and in fact you'll see a lot
of reports about "locale::facet::_S_create_c_locale name not valid"
exception thrown by boost - see e.g. the last comment here
https://github.com/udoprog/c10t/issues/203
There is nothing we can do at the level it surfaces (sco
1 - 100 of 186 matches
Mail list logo
