[Bug 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1
How am I supposed to disconnect web server that is online? It's a joke I guess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673247 Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1673247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
Any updates? As far as I can see the problem still exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1667512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
Have the same problem since yesterday. I'm having 4.4.0-47 4.4.0-59 4.4.0-62 4.4.0-64 installed. I was trying to upgrade my system yesterday and 4.4.0-66 was about to be installed, but it hangs on update-initramfs or to be more precise it's hanging on "Building cpio" when running update-initramfs -u -v Problem is related probably to last 2 upgrades which I did. Here is the list of packages installed yesterday (aptitude): [REMOVE, NOT USED] ubuntu-core-launcher:amd64 2.22.6 [UPGRADE] snapd:amd64 2.22.3 -> 2.22.6 [UNCONFIGURED] linux-generic:amd64 4.4.0.66.70 [UNCONFIGURED] linux-headers-4.4.0-66:amd64 4.4.0-66.87 [UNCONFIGURED] linux-headers-4.4.0-66-generic:amd64 4.4.0-66.87 [UNCONFIGURED] linux-headers-generic:amd64 4.4.0.66.70 [UNCONFIGURED] linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 [UNCONFIGURED] linux-image-extra-4.4.0-66-generic:amd64 4.4.0-66.87 [UNCONFIGURED] linux-image-generic:amd64 4.4.0.66.70 [UNCONFIGURED] linux-libc-dev:amd64 4.4.0-66.87 [UNCONFIGURED] lxd:amd64 2.0.9-0ubuntu1~16.04.2 [UNCONFIGURED] lxd-client:amd64 2.0.9-0ubuntu1~16.04.2 [UNCONFIGURED] mdadm:amd64 3.3-2ubuntu7.2 [UNCONFIGURED] snap-confine:amd64 2.22.6 [UNCONFIGURED] ubuntu-snappy-cli:amd64 2.22.6 here is the list of previous upgrade (apt): Start-Date: 2017-02-21 23:48:52 Commandline: apt upgrade Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic) Upgrade: lxc-common:amd64 (2.0.6-0ubuntu1~ubuntu16.04.2, 2.0.7-0ubuntu1~16.04.1), libssh2-1:amd64 (1.5.0-2, 1.5.0-2ubuntu0.1), libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), linux-libc-dev:amd64 (4.4.0-62.83, 4.4.0-64.85), linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), snapd:amd64 (2.21, 2.22.3), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), snap-confine:amd64 (2.21, 2.22.3), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), lxd:amd64 (2.0.8-0ubuntu1~ubuntu16.04.2, 2.0.9-0ubuntu1~16.04.1), liblxc1:amd64 (2.0.6-0ubuntu1~ubuntu16.04.2, 2.0.7-0ubuntu1~16.04.1), libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), ubuntu-core-launcher:amd64 (2.21, 2.2 2.3), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), ubuntu-snappy-cli:amd64 (2.21, 2.22.3), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, 1:9.10.3.dfsg.P4-8ubuntu1.5), linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), lxd-client:amd64 (2.0.8-0ubuntu1~ubuntu16.04.2, 2.0.9-0ubuntu1~16.04.1), lxcfs:amd64 (2.0.5-0ubuntu1~ubuntu16.04.1, 2.0.6-0ubuntu1~16.04.1) End-Date: 2017-02-21 23:49:31 I'm able to update initrd.img file using following command, it doesnt hang on that "Building cpio": mkinitramfs -v -c -k 4.4.0-66-generic -o /tmp/initrd.img.tmp I'm not planning to restart server during next few weeks, so I'm unable to check if it's running. Right now I'm working on 4.4.0-62. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1667512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974251] [NEW] libapache2-mod-shib module doesn't work with 2.4.52
Public bug reported: ubuntu release: Jammy apache version: 2.4.52-1ubuntu4 libapache2-mod-shib: 3.3.0+dfsg1-1 Apache 2.4.52 is unable to connect to shibboleth - shibd (version 3.3.0) process. Downgrade of shibboleth package (compiled from sources - 3.2.2) doesn't resolve the issue. Apache returns Error 302 each time when trying to open some webpage and in error log there is only this message: Cannot connect to shibd process, a site adminstrator should be notified Apache upgrade to 2.4.53 from PPA solves the problem. Didn't found anything in apache changelog regarding that issue, but probably related to one of found bugs in 2.4.52 ** Affects: apache2 (Ubuntu) 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/1974251 Title: libapache2-mod-shib module doesn't work with 2.4.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974251] Re: libapache2-mod-shib module doesn't work with 2.4.52
Unfortunately you need to have a website with already running configuration for shibboleth. I'm working with very complex configuration that we have for our customers and wasn't able to make it working after upgrading Ubuntu from 18.04 (that part is running in docker), but since apache upgrade solves the issue I guess this bug here can stay for others who would be facing similar issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974251 Title: libapache2-mod-shib module doesn't work with 2.4.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974251] Re: libapache2-mod-shib module doesn't work with 2.4.52
Found what is the issue, looks like libpam-systemd package was missing in the system, discovered that while installing other libraries, after installation communication between shibboleth and apache works as expected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974251 Title: libapache2-mod-shib module doesn't work with 2.4.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974251] Re: libapache2-mod-shib module doesn't work with 2.4.52
After more digging I've found that it's not the libpem-systemd package itself, but one of commands that comes from systemd. systemd-tmpfiles --create That command is executed during system startup and it sets permissions on a lot of system directories, according to some configuration file. One of those directories is this one: root@apache:~# ls -ld /run/shibboleth/ drwxr-x--- 2 _shibd _shibd 4096 May 27 12:18 /run/shibboleth/ After running the systemd-tmpfiles --create permissions of that directory are changed to following: root@apache:~# ls -ld /run/shibboleth/ drwxr-xr-x 2 _shibd _shibd 4096 May 27 12:18 /run/shibboleth/ so in the end running chmod 755 on /run/shibboleth solves the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974251 Title: libapache2-mod-shib module doesn't work with 2.4.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769016] Re: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved
I had the same issue, I was also looking at nsswitch.conf but only after finding this post and adding the 'resolve' to that conf it started working normally. I had an other, custom vpnc-script and that one also worked but can't find it now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769016 Title: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1769016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
