Dropped severity.
While there are no updates to snapd newer than your ISO, this bug won't
occur at all. Also there is a simple workaround documented at the top.
And alternative workarounds are possible too.
** Changed in: snapd (Ubuntu)
Importance: Critical => High
** Summary changed:
- snap
** Tags added: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
Title:
snapd on cosmic never finishes installing/updating. Can't install any
other
On a new install from Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913)
the update+upgrade installed the new snapd (2.35.2+18.10) over (2.35.1+18.10)
and now i have all the default snap working
corrado@corrado-HP-p4-cc-0913:~$ snap list
Name Version Rev Tracking Publ
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
Title:
snapd on cosmic never finishe
Same issue here, I do "sudo pkill snapd" every time dpkg gets stuck on
setting up snapd, at least this lets other packages to continue
installing/updating.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
htt
Note that according to Oliver in the above linked bug #1785388 this is
currently intentional in Cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
Title:
snapd
workaround is easy: modify /var/lib/snapd/seed/seed.yaml and restart snapd
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1785388
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.
Bug 1781513 is on bionic, so that's not the same issue as this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
Title:
snapd on cosmic never finishes installing/upd
We found the root cause now and work on a fix. sorry for the trouble -
Note that this is a "cosmic" specific issue. I'm exploring workarounds
now to unblock you.
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member o
Unfortunately the machine is a friend's and not in my hands anymore, but
I can probably check next weekend if necessary
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
the ps output I addet to my bug
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791087 is from a
laptop install
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
I think I've hit this with most/all cosmic desktop installs for the past
few months.
My uncertainty only comes from the fact that you won't hit the bug
until/unless the system needs to update snapd after that. So maybe a
good test is to start with a cosmic image that is older than the last
snapd u
Michael, I am not Alex but I had the same on a completely fresh Cosmic
install from the Desktop image to a new latop (Asus ZenBook Flip
UX561UD). No special polkit/pam configs, after the install was finished
I ran an update and there it was
--
You received this bug notification because you are a
What we see in the ps output is that for some reason it seems like
systemctl prompts for a password. Which is unusual because apt/dpkg runs
as root so there should be no need for this. Any further hints for us?
Are these desktop or server installs?
--
You received this bug notification because yo
Hey Alex first, sorry for the trouble you have! We do run ~2800 tests
which each branch merged or release. This includes an automatic upgrade
test. Unfortunately the hang is not reproducible for everyone it seems,
neither our automatic tests nor I in a VM have managed to trigger this
hang. But we a
This happend to me repeatedly on Ubuntu Bionic too, making snaps
uninstallable. How can such bugs come through. They can be easily
catched with automated tests. I remember this bug happened to me after a
fresh Ubuntu Bionic installation. An now again after updating snap.
Please automate your tests!
I added output from "ps afx" in my bug:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791087
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776622
Title:
snapd on
Thanks for your bugreport. The output of "ps afx" when this hangs would
be great to get an idea why the dpkg process blocks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/17
again with new snapd from proposed
Setting up snapd (2.35.1+18.10) ...
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
--
You received this bug notification because you are a member of Ubuntu
Touch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
Since ctrl-c doesn't seem to work to interrupt the upgrade, I had to
ctrl-z and I checked pstree. It seems that the init script runs
systemctl, which runs systemd-tty-ask-password-agent, and that hangs,
never presenting a prompt. I tried to kill that and it became a zombie,
never being reaped by
21 matches
Mail list logo