[Touch-packages] [Bug 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root

** Changed in: systemd (Ubuntu) Status: Expired => New -- 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/1891394 Title: systemd breaks upgrade with useless error if /v

[Touch-packages] [Bug 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root

Var was owned by the user I usually log in as. I don't know why, yes it's weird, I fixed it. I don't think that justifies this package's upgrade braking behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ub

[Touch-packages] [Bug 1895686] Re: blkid always hangs, launched by dpkg --configure -a

** Description changed: I noticed last night that package install fails. Then I noticed - processes running from an automatic upgrade that ran on September 9th. + processes running from an automatic upgrade that ran on September first. Whenever I run "dpkg --configure -a", it gets stuck on bl

[Touch-packages] [Bug 1895686] Re: blkid always hangs, launched by dpkg --configure -a

** Attachment added: "Full output of that strace" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+attachment/5411074/+files/blkid.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu.

[Touch-packages] [Bug 1895686] [NEW] blkid always hangs, launched by dpkg --configure -a

Public bug reported: I noticed last night that package install fails. Then I noticed processes running from an automatic upgrade that ran on September first. Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging. When I run the same command manually through strace, it seems to get

[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot

I think I had the same problem. I think it was fixed with "chown root:root /var". Related to this: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394 I think it also caused screen to be unusable until it was run by root. -- You received this bug notification because you are a membe

[Touch-packages] [Bug 1891394] [NEW] systemd breaks upgrade with useless error if /var is not owned by root

Public bug reported: I just upgraded from 16.04 to 18.04. The upgrade broke. The error, from systemd, was: "Unsafe symlinks encountered in /var/log/journal, refusing." That directory was empty. The fix was "chmod root:root /var". Yes, it's weird that my /var wasn't owned by root, but upgrade

[Touch-packages] [Bug 1436558] Re: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of pa

I'm not certain I had the same problem, but the workaround I used was: dpkg --force-depends -r purge libldap-2.4-2:amd64 libldap-2.4-2:i386 apt-get -f install Because apt-get purge refuses due to dependencies. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 565364] Re: pinning a specific package does not work

Nice, that (debian) bug is 10 years old. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/565364 Title: pinning a specific package does not work Status in apt package in Ubuntu