** Changed in: snapd
Status: New => 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/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about t
** Changed in: snapd (Ubuntu)
Status: In Progress => Invalid
--
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 test failing with latest bionic updates
To manage notificat
Hi Alfred,
Any chance to have journal log (journalctl -u snapd) from the time of
upgrade?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967479
Title:
snaps lost connections during 22.04 up
To summarize, there are two issues:
1. snaps were not mounted on restart for some reason
2. this lead to loosing all auto-connected interfaces on snapd start (because
snap.yaml files couldn't be read from disk)
The cause of problem #1 is unknown and we had a couple of reports about
this in the pa
** Changed in: snapd
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/bugs/1943853
Title:
Ubuntu update disconnected all snaps
To manage notifications about this bug
** Changed in: snapd
Status: Incomplete => Confirmed
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Summary changed:
- Recent update DELETED SNAP PROGRAMS
+ Ubuntu update disconnected all snaps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943853
Title:
Ubuntu update disconnected all snaps
T
Ah, what I suggested in comment #18 would only re-create "system"
connections (such as desktop, audio-playback etc) provided by snapd, but
the other problem is with gnome-3-28-1804 and gtk-common-themes content
provider slots. For those, removing and installing them back should re-
create their aut
Also, could you try:
$ snap refresh --beta snapd
(afterwards you can do snap refresh --stable snapd)
and see if it helped restore the connections?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194385
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873679
Title:
Snap support for non /home homedirs
To manage notifications about thi
@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
@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
** 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.
@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
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
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
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
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
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
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'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
** 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
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
*** 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
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
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.
** 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
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
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
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
@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,
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
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
@Dan: This is an interesting observation.. I'll bring it up with the
team. Thank you.
** 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, which is subscribed to
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865519
Title:
apparmor depends on python3
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.
-
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
** 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
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
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
** 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
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640523
Title:
Warn about leading "0" (octal) in snap.yaml?
To manage notifications about this
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
** 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
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
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
*** 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)
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
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
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
** 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
** 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
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
*** 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
*** 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
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
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
** 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
** 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
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/1724316
Title:
"Sorry, something went wrong cannot authenticate to snap store ..."
w
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
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
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
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/
*** 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
@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
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
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
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
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
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
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:/
** 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
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)
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.
I haven't tested the attached branch yet; let's coordinate that since I
think you're working with a silo on all this.
** Branch linked: lp:~stolowski/unity-scopes-shell/art-uri-snap-root
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: unity-scopes-shell (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.
https://bugs.launchpad.net/bugs/1639249
Title:
Result art not displayed when
A quickfix in the shell plugin may fix it for the initial approach
(scopes in same snap as the shell), but it gets more complicated when
scopes are in separate snaps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** 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
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):
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
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
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
Please make sure you have latest everything from xenial overlay ppa
(looks like maybe your libunity scopes lib or unity-plugin-scopes are
outdated); tested with unity-scope-tool and it works here. This is what
I have:
ubuntu@ubuntu-xenial:~$ apt-cache policy libunity-scopes1.0
libunity-scopes1.0:
Hi Brian, I started working on the implementation in unity-scopes-shell
at the time we discussed this, but it turned out to be more complex than
expected.
First off, the solution with preview_by_key I suggested above turned out
to be a no-go, because it was incompatible with how preview actions wo
*** This bug is a duplicate of bug 1604356 ***
https://bugs.launchpad.net/bugs/1604356
** This bug has been marked a duplicate of bug 1604356
symlink creation over and over on install, creates file too long situation
--
You received this bug notification because you are a member of Ubuntu
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** 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/1622782
Title:
** 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/1625376
Title:
Get required Snap interfaces from store
To manage notifications about this b
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
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
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 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
** 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
** 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
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: 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
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
1 - 100 of 186 matches
Mail list logo
