[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666122
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666122
Title:
package snapd 2.22.2~14.04 failed to install/upgrade: Unterprozess
neues pre-removal-Skript gab den Fehlerwert 5
Thanks for your efforts up to now.
I'm aware of the disk issue, but this concerns the partition where Windows is
installed(Dual Boot System).
If Windows is not entirely shut down, Ubuntu marks the partition as unstable
and can not mount it.
I will add the source lists as soon as I'm home.
--
** 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/1666122
Title:
package snapd 2.22.2~14.04 failed to install/upgrade: Unterprozess
Looking at the logs again (thanks for the pointer Mark) I see that the
pre-removal script for snapd from the 14.04 archive has failed.
** Changed in: snapd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Reporter, can you please add your `/etc/apt/sources.list` and
/etc/apt/sources.list.d` to the bug report. We recently saw some people
update to Xenial in a way the would leave a Trusty repository enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not sure that's the root cause since the reporter appears to believe the
machine is otherwise healthy. Something that doesn't affect other
software but does affect snapd is worth digging in to.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looks like the disk on the reporter machine has some issues. The log is
full of:
[ 48.308366] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
[ 48.308372] sd 6:0:0:0: [sdb] tag#0 Sense Key : Hardware Error [current]
[descriptor]
[ 48.308375] sd 6:0:0:0:
