*** This bug is a duplicate of bug 1035045 ***
https://bugs.launchpad.net/bugs/1035045
** This bug has been marked a duplicate of bug 1035045
bzr refused to commit systemd-escaped filenames
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: snappy
Status: In Progress => 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/1560942
Title:
Support swap
To manage notifications about this bug go to:
https://bugs
@Norbert, which snaps? I've only heard about electron snaps losing some
themeing in 19.10 (unrelated to snap vs non-snap afaik).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585332
Title:
Graphica
er, i meant pwd%3Dfoo, obvs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579652
Title:
snap ignores the proxy environment variables
To manage notifications about this bug go to:
https://bugs.laun
I've just checked, and both pwd=foo and pwd%3D=foo in the userinfo part
of the url get picked up with no issue (and amount to the same thing).
What is your proxy seeing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Nah, on the contrary, there is nothing for snapd to do here; it already
does what's wanted (and has from day one). I'm removing snapd from the
bug ...
of course if I got something wrong, please add it back and let us know
:-) (setting it to new will get it noticed soonest)
** No longer affects: s
Hello! Thank you for taking the time to report this issue.
Could you tell me what you see when you go to
https://www.fastly-debug.com/
?
** Also affects: snapd
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
** Tags added: papercut
** Package changed: snapd (Ubuntu) => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This is inherited from our use of gpg. There doesn't seem to be a way to
have unattended key generation not strip whitespace from the end of the
passphrase (or any other option for that matter).
Is there anything we can do? (and is it worth it?)
** Changed in: snapd (Ubuntu)
Status: New =
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
Oh dear, sorry we didn't reply to this in a timely manner.
Things have changed enough that I don't think this happens any more, but
if it does, please re-open this (set it to New again)? We're trying to
pay closer attention to bugs now, at least New ones, so we catch this
sort of thing earlier.
F
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
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 => 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/1691782
Title:
snapd 2.26.1+17.10 ADT test failure with linux 4.11.0-3.8
To manage not
(please set this back to New when you respond...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688335
Title:
Classic confinement doesn't work with custom environment
To manage notifications about
Marking as invalid for snapd itself, as it's not a bug in snapd --- the
snap needs to do a bit of work to pick up themes.
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Hello!
I'm sorry it's taken this long to get back to you on this.
I'm not able to reproduce your issue: with a snap.yaml of
name: test-snapd-classic-confinement
version: 1.0
confinement: classic
apps:
sh:
environment:
MAGIC: xyzzy
command: bin/sh
when I run test-snapd-classic-co
** Package changed: snapd (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686631
Title:
[Ubuntu-gnome] if an app is uninstalled and has a snap and deb it
display
Chatted with the team a bit. There are two ways forward that we can see:
* somehow fix gpg, or the way we call it, to not strip whitespace from
the end of values. This looks to be a lot of work, and not a lot of
benefit, so we think this would be a Low priority task.
* detect a passphrase that st
** Changed in: snapd (Ubuntu)
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/1707195
Title:
snapd 2.26.10+17.10 ADT test failure with linux 4.12.0-9.10
To manage n
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714024
Title:
unable to refresh snap to --classic: snap has no updates
available
To man
** 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/1705988
Title:
snap install --classic juju fails
To manage notifications about this bug
Marking as invalid because I understand the issue to have been due to
having proposed enabled, and the issue itself wouldn't happen outside of
that.
If this is not the case, and there is something to fix, please re-set to
New (and explain...)
** Changed in: snapd (Ubuntu)
Status: New => In
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
Do you still have this problem, and if so, could you share the snap (or
how to build it)? This way we might be able to reproduce the issue.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Changed in: snapd (Ubuntu)
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/1705666
Title:
snapd 2.25 ADT test failure with linux 4.4.0-87.110
To manage notificat
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
I agree this would be nice.
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
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/b
Sorry it's taken this long to respond to this bug! We're trying to bring
our New bugs down close to zero, to catch these things early...
hopefully we get better at it.
We've added 'snap run --strace' (and 'snap run --gdb') to help debugging
this sort of thing. Hopefully that fixes this.
** Change
I hope we've improved our documentation about this. I've marked the
ubuntu/snapd task of the bug as Invalid as the issue isn't about the
snapd package in Ubuntu. If you think there is more we should do, please
let us know.
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You receiv
** Changed in: snapd (Ubuntu)
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/1730950
Title:
snapd 2.28.5+17.10 ADT test failure with linux 4.14.0-6.8
To manage not
I don't understand: uname says you're running the 'stable' kernel, so
all should be well?
** 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/1
Sorry it's taken us so long to get back to you on this.
On 2.41 I don't see this issue. I also don't see the app doing anything
useful beyond using a lot of CPU, so there might be an issue in the snap
itself.
Marking as Invalid for snapd, please set back to New if you think I'm
wrong on this (or
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
** Changed in: snapd (Ubuntu Xenial)
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/1699768
Title:
eh... i'm uncomfortable about closing this.
the bug is still there, we're still offering these bad completions.
'snap interfaces' is deprecated but not removed. The fix should be
straightforward (even though we expect it not to live long, it might...
temporary workarounds living forever and all th
** 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/bugs/1779190
Title:
Snap search uses Go-http-client/1.1 as UserAgent instead of the sna
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
** Package changed: snapd (Ubuntu) => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779190
Title:
Snap search uses G
The problem is that you saw a .desktop file inside the snap and assumed
that your desktop environment was using that directly.
It's not; that would be dangerous. snapd takes those .desktop files, and
sanitises and transforms them, and the resulting sanitised and
transformed files are the ones pick
No, I don't think we should document this. It's unsupported, and can and
will break things. Only for the brave.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810688
Title:
Snap-installed .desktop i
If you have this issue, please share the output of
snap info --verbose /var/lib/snapd/seed/snaps/* | egrep 'name|base'
thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819427
Title:
Disco
OK, unless anybody comes up with evidence to the contrary, I'm going to
say that what was happening was this:
Some isos have gone out with snaps that had `base: core18`, but without
seeding `core18`. This is not supported, and will cause seeding to hang.
Unless somebody can positively point to th
snapd will not work properly with users' homes that are unavailable if
the user is not logged in. As a workaround, schedule refreshes to only
happen when all the local users are logged in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
@J.Snow, don't run binaries from inside the snap directly, you won't
have the right LD_LIBRARY_PATH and all the rest of the environment
needed to run the snap.
Similarly, don't install strict snaps as classic. You'll be picking up
random libraries instead of the ones tested and shipped in the snap
Thank you for that.
Could you tell me the output of
type vlc
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810027
Title:
Snaps won't start - stack smashing detected
To manage notifications about
What's the output of "journalctl --system -u snapd"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
Fails to work on a fresh 19.04 install
To manage notifications about this bug go to
** 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/1825437
Title:
Fails to work on a fresh 19.04 install
To manage notifications about this
Yes, mvo lives in a future in which he's already implemented that
feature, whereas us mere mortals are stuck waiting for it to arrive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
sn
just don't read the commit messages and you'll be fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted seed.yaml on Ubuntu 19.04
To manage notification
Yes, only terminals that a snap can find will work. For that it needs to
be either in the base snap (core or core18, depening), or in the snap
itself (or somewhere the apps in the snap have access to).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: snapd (Ubuntu)
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/1834631
Title:
ncurses snaps won't launch with "st-256color" as the termname
To manage no
if you have a terminal not supported in the base, it should be enough to
drop the terminfo file into the right place:
~$ TERM=xyzzy msnake
Error opening terminal: xyzzy.
~$ mkdir -p ~/snap/msnake/current/.terminfo/x
~$ cp /lib/terminfo/x/xterm-256color ~/snap/msnake/current/.terminfo/x/xyzzy
~$ T
I suspect these images have a broken seed.yaml. Could somebody attach
that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828500
Title:
snapd fails always in Optimised Ubuntu Desktop images availa
To confirm, (from memory), sudo snap info --verbose
/var/lib/snapd/seed/snaps/*.snap | grep base:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828500
Title:
snapd fails always in Optimised Ubuntu
Yeah. The images are broken, because they ship a broken seed.yaml. Who
creates the images? That's the project this bug needs to be assigned to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828500
Ti
yeah. That seed.yaml is missing core18, and those snaps need it AFAIK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828500
Title:
snapd fails always in Optimised Ubuntu Desktop images available i
** Package changed: snapd (Ubuntu) => livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828500
Title:
snapd fails always in Optimised Ubuntu Desktop images available in
Micros
I haven't yet tried to reproduce this with an upstream kernel, but given
that it's affecting arch users with 5.2 as well, it's fairly likely to
be there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Public bug reported:
On a system running a 5.2 kernel, doing a large number of mounts of
squashfs filesystems in parallel results in the mounts getting out of
sync with their backing devices.
To reproduce,
https://paste.ubuntu.com/p/VCpzGxvy6h/
this breaks people with ~40 snaps (easily achievab
The mainline builds for i386 and amd64 are failing right now so not sure
I can do more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836914
Title:
Doing multiple squashfs (and other loop?) mounts
*** This bug is a duplicate of bug 1828500 ***
https://bugs.launchpad.net/bugs/1828500
** This bug has been marked a duplicate of bug 1828500
snapd fails always in Optimised Ubuntu Desktop images available in
Microsoft Hyper-V gallery
--
You received this bug notification because you ar
Could you share with us whatever data you have that led you to the
conclusion that it was snapd writing? Also the output of 'snap version'
and 'snap list' might be helpful.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a memb
Apparently the message
argument "foo"'s "bar" should be wrapped in <>s
is ambiguous, and the ru translator has taken it to mean that it should
look like literally "s" instead of "".
We'll update the message to say "should start with < and end with >".
We'll also add code to drop the s if it mat
As adding --classic has security implications, we want you to think
about what it means, and only add it if you're ok with that. Actively
discouraging cut-and-paste that'll open security holes.
** Changed in: command-not-found (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this b
Note we're not using "English" quotes (“”), but rather the ASCII
"quotation mark" glyph, which is a compromise.
The use of guillemots is recommended but not obligatory in Spanish¹, and
I think every language has their preferred quotations, including “foo”,
„foo”, «foo», »foo«, ‹foo›, 『foo』, ...
A
Reading the code, the English original is wrong also. Apologies for
that; we'll fix.
It should read like "command", with Advise being a verb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808213
Tit
The message is scary, but it's not really a problem; snapd will retry
later.
Let's make this bug about making the message less scary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762190
Title:
st
Could you help me reproduce this, please? I've tried both those snaps in
18.10 just now and neither of them crash the way you report.
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
igor, is this still the case? If so, can you give us the information
zyga asked for?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757284
Title:
Several snap apps fail to launch
To manage notifica
Yes, snapcraft.io tells you to use sudo, as not everywhere that can use
snaps has polkit. You're on Ubuntu, though, so polkit should just work.
In any case, sudo should also work :-)
Is there anything 'interesting' about your system, that would set it
apart from a standard default Ubuntu installat
I don't know much about this, but I'm asking different people and I'll
answer here as I find out.
We don't have fwupdate in ubuntu core itself:
$ find EFI -type f
EFI/boot/grubx64.efi
EFI/boot/bootx64.efi
EFI/ubuntu/grubenv
EFI/ubuntu/grub.cfg
it is used in some _customer
What are the contents of seed.yaml?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
snapd didn't initialize all the seeded snaps
To manage notifications about this bug go to:
https://b
Note that seed change is still ongoing (it's still got tasks in Doing
state). You can watch the progress with 'snap watch --last=seed'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
s
As a workaround, in seed.yaml, ensure content providers are before the
snaps that need them; the seeding step does not sort things.
It's unclear whether it should, but at least we should warn about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
*** This bug is a duplicate of bug 1662552 ***
https://bugs.launchpad.net/bugs/1662552
** This bug has been marked a duplicate of bug 1662552
snaps don't work with NFS home
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Could you attach the output of 'journalctl -u snapd'? There's a
traceback in there, that's only partially visible in the 'status'
output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
I wonder what happened to the traceback you clearly have in the
`systemctl status` you pasted in the description.
Anyway, is there anything special about this device?
Can you show us the output of `snap version`? what about `snap changes`?
--
You received this bug notification because you are a
Boo! I thought you'd found an interesting one! :-)
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784843
Title:
snap list: unexpected fault address 0xf1f0
To manage notifications ab
Today, snap updates (and any other changes under snapd's control) are
visible in 'snap changes' for a few days.
After that they are cleaned up, to stop snapd from using up too many
system resources.
We are aware that people want to be able to keep them around for longer,
but have not gotten aroun
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757284
Title:
Several snap apps fail to launch
To manage notifications about this
It's always bee the case that a properly configured kernel is needed for
snapd to work. There even have been features added, and bugs fixed, in
the kernel as a direct result of needing features working for snapd (and
in those cases the Ubuntu kernel has often shipped the patches before
they were up
Could you attach the output of `journalctl -u snapd`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782602
Title:
On slow boots snapd falls into a initialization loop
To manage notifications about
*** This bug is a duplicate of bug 1782616 ***
https://bugs.launchpad.net/bugs/1782616
I think this is probably a dupe of lp:1782616; marking it as such.
** This bug has been marked a duplicate of bug 1782616
long delay (40 seconds) in boot due to snapd.seeded.service
--
You received thi
Could you add the output of «journalctl -u snapd» to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779948
Title:
Snapd gets stuck when starting Ubuntu.
To manage notifications about this
There's something very strange going on.
This is what I get:
$ snap install atom --classic
atom 1.28.2 from 'snapcrafters' installed
$ snap install atom --classic
snap "atom" is already installed, see 'snap help refresh'
$
the 'already installed' error is returned before even looking at the
sto
Yep! reproduced it:
$ snap install atom –classic
error: store.SnapNotFound with 2 snaps
that _is_ a terrible error.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: snapd (
I've added code to check for typographical dashes and warn the user:
https://github.com/snapcore/snapd/pull/5524
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782110
Title:
unhelpful error message
For reference:
$ snap install ––help
Your command included some characters that look like dashes but are not:
"snap install \u2013\u2013help"
in some situations you might find that when copying from an online source such
as a blog you need to replace “typographic” dashes and quotes with their
Em dashes cannot be part of a snap name.
They _could_ be part of an intentional 'snap set' command, something like
snap set mysnap foo=—o—
in which case, if the "snap set" fails, the user will get the above message,
followed by whatever error. Like so:
$ snap set bofh foo=—o—
Your command incl
I removed the "snap" package bug task, as I doubt this bug affects the
gene finder.
** No longer affects: snap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should dep
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Package changed: snapd (Ubuntu) => snapd
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Status: New => In Progress
--
You received this bug notification becau
Hello Turan, thank you for the bug report!
could you add the output of “journalctl -u snapd” to this?
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685755
Title:
Can install snaps
To
Note the user has also reported this in the forum:
https://forum.snapcraft.io/t/cant-install-snap-app/376/3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685755
Title:
Can install snaps
To manage
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progr
$ /tmp/snp info quagga
name:quagga
summary: "Quagga BGP/OSPFv2/OSPFv3/ISIS/RIP/RIPng/PIM routing daemon"
publisher: osr
channels:
candidate: 1.0.20160315-rc1-git.c01f37e (4) -
beta: 1.0.20160315-rc1-git.c01f37e (4) -
edge: 1.0.20160
pgrade log present (probably fresh install)
** Affects: apt (Ubuntu)
Importance: Undecided
Assignee: John Lenton (chipaca)
Status: Incomplete
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Installing a package is not a CPU-intensive process; it's an IO-
intensive one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585403
Title:
please support parallel operation
To manage notification
Sciri, how is this not a dupe? In both cases it's bzr having an
expecation about what's a valid filename that is not supported by
systemd mount units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650
Where are you getting shellcheck 0.4.4 to run under travis? In Ubuntu
0.4.4 is from 17.04, and afaik travis is still on 14.04. So it could
indeed be that you're running a shellcheck built for a newer kernel than
you have.
** Changed in: shellcheck (Ubuntu)
Status: Confirmed => Incomplete
-
I just tested, and running shellcheck 0.4.4 from artful (not 17.04; my
bad: 17.10) on 16.04 or 14.04 will print that error. Downloading 0.4.4's
package sources from http://packages.ubuntu.com/artful/shellcheck and
rebuilding it does not print that error.
Closing this as Invalid; afaict it's not th
Omiting architecture makes it default to amd64 afaik; you'd need to know
the list of architectures of the store you're querying, and loop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701232
Title:
301 - 400 of 966 matches
Mail list logo
