[Bug 1458084] [NEW] puppet outdated: can't install ed25519 ssh-key
Public bug reported: Hi, when using a ssh_authorized_key resource to install public keys in the authorized_keys files, it works with rsa, but not with ed25519 keys: Error: Failed to apply catalog: Parameter type failed on Ssh_authorized_key[root-hadmut-ed25519@home]: Invalid value "ssh-ed25519". Valid values are ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521. at /etc/puppet/modules/hadmut/manifests/server/netzdienste/sshd.pp:141 Wrapped exception: Invalid value "ssh-ed25519". Valid values are ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521. The nist curves are considered insecure . Puppet should be able to install keys that are still seen as secure. regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: puppet (not installed) ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 23 01:23:28 2015 InstallationDate: Installed on 2014-08-06 (289 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) SourcePackage: puppet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: puppet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1458084 Title: puppet outdated: can't install ed25519 ssh-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1458084/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
Adding the following to /etc/named/named.conf.options seems to have
fixed this problem:
listen-on { 127.0.0.1; 167.114.159.29; };
This seems like a bug to me. Maybe switching to systemd created a subtle
change in order of network config + named + lxc-net start.
This is the first time I've had to edit bind's config files to have LXC
networking start at boot time.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458063
Title:
Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because
named listening to UDP on LXC address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] [NEW] Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
Public bug reported: This is a clean Vivid install (rather than upgrade). Maybe I munged something + for the life of me nothing comes to mind. /var/log/syslog shows somehow bind is polluted with dnsmasq addresses? All packages updated. net8-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid net8-rmt# uname -a Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux net8-rmt# pkg-list | egrep -e lxc -e cgroup cgroup-bin 0.38-1ubuntu2 cgroup-lite 1.10 libcgroup1 0.38-1ubuntu2 liblxc1 1.1.2-0ubuntu3 lxc 1.1.2-0ubuntu3 lxc-templates 1.1.2-0ubuntu3 lxcfs 0.7-0ubuntu4 lxctl 0.3.1+debian-3 python3-lxc 1.1.2-0ubuntu3 Behavior is this. 1) After reboot, lxcbr0 is missing 2) /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart reports 10.0.3.1 (set in /etc/default/lxc-net ) as being in use. 3) netstat reports bind/named has the address, at least UDP, no TCP. 4) /var/log/syslog from last boot shows this... net8-rmt# grep 10.0.3.1 /var/log/syslog May 22 16:03:01 ns515383 named[1355]: listening on IPv4 interface lxcbr0, 10.0.3.1#53 May 22 16:03:02 ns515383 ntpd[1453]: Listen normally on 5 lxcbr0 10.0.3.1 UDP 123 May 22 16:03:04 ns515383 lxc-net[1360]: dnsmasq: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:04 ns515383 dnsmasq[1768]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:06 ns515383 ntpd[1453]: Deleting interface #5 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs May 22 16:21:04 ns515383 dnsmasq[10991]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:21:30 ns515383 dnsmasq[11156]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:24:15 ns515383 dnsmasq[12092]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:25:36 ns515383 dnsmasq[12576]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:29:54 ns515383 dnsmasq[14015]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:34:55 ns515383 named[1355]: no longer listening on 10.0.3.1#53 May 22 16:35:10 ns515383 ntpd[1453]: Listen normally on 9 lxcbr0 10.0.3.1 UDP 123 May 22 16:35:26 ns515383 ntpd[1453]: Deleting interface #9 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=16 secs May 22 16:52:50 ns515383 ntpd[1453]: Listen normally on 11 lxcbr0 10.0.3.1 UDP 123 5) Nothing in named config referencing the LXC IP. 6) Then after server minutes, named stops listening to this address, at which time /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart begins working as expected. 7) If /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop is issued + service bind9 restart issued, named no longer attempts to connect to 10.0.3.1 so all's well. Any suggestions on why named might be grabbing the LXC address at boot time are appreciated. I reported this as a bug, because none of the named config files reference the LXC IP address, so to me, named should never touch this address. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time + Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening on LXC address ** Summary changed: - Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening on LXC address + Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1458063 Title: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
Oh... Maybe the problem is lxcbr0 is up'ed before named starts. Then if named listens on 0.0.0.0 makes sense it would glom onto the lxcbr0 address too. I'll modify named's config files + reboot + see if this fixes the problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1458063 Title: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1258219] Re: smbclient 'put' fails with absolute path to local file
I know this thread is quite old, but just in case... Sorry, Robie, but I don't understand you. What could be the advantage or intentionality behind it? I mean, smbclient is a linux program and the put command is to copy a local file (so, from linux path) to a remote computer. Why should you need to consider any kind of path manipulation? Regards -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1258219 Title: smbclient 'put' fails with absolute path to local file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1258219/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1263181] Re: curtin discovers HP /dev/cciss/c0d0 incorrectly
this is believed to be fix-released in wily. I'd appreciate someone telling me if it is not working. ** Changed in: curtin Status: Triaged => Fix Committed ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New => Fix Released ** Changed in: curtin (Ubuntu) Importance: Undecided => Medium ** Also affects: curtin (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Trusty) Status: New => Confirmed ** Changed in: curtin (Ubuntu Vivid) Status: New => Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: curtin (Ubuntu Vivid) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1263181 Title: curtin discovers HP /dev/cciss/c0d0 incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1263181/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
This is a patch I created, by backporting 2.4 commits for DH keys to 2.2, to solve the DH keys too small issues on certs. Adding here in case it helps anyone. ** Patch added: "DH key sizing backport from 2.4" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+attachment/4402571/+files/ssl_dhparams.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
I'll work on releasing this for precise next week. ** Changed in: apache2 (Ubuntu Precise) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4
Well, either squid has to move up to 3.4+ which you said is a non- starter, or squidGuard has to move back down to 1.5-2 which the Debian guys aren't likely to do. So that leaves us nowhere. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1448149 Title: Squid 3.3.8 incompatible with squidGuard 1.5-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1448149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457754] Re: "E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1457754 Title: "E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1457754/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457957] [NEW] puppet uses upstart for service status checks in vivid
Public bug reported: After upgrading one of my servers to 15.04/vivid (from original 14.10/utopic install), I had a failing puppet job. The error message is: Error: /Stage[main]/Main/Service[ssh]: Could not evaluate: Execution of '/sbin/status ssh' returned 1: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused After some research it seems that this happens with all daemons that have an upstart config file hanging around in '/etc/init/'. Puppet checks for existence of that file, and then assumes that it should issue the '/sbin/status ' command in order to check the service status. For all services that don't have an upstart conf installed, puppet uses '/etc/init.d/ status', which works perfectly (for ssh and munin-node, the two services I used while verifying the behavior). As I assume that we cannot expect to have all services drop the upstart config in their vivid packages (I'm not sure about the status of upstart support in vivid), the best fix should be to have puppet check for '/etc/init.d/' before trying '/etc/init//.conf', at least on vivid. puppet-common version: 3.7.2-1ubuntu2 Note: even setting service 'hasstatus => no' and 'status => /etc/init.d/ssh status' in the puppet Service definition does not force puppet to not issue the command (which probably should be a separate bug). ** Affects: puppet (Ubuntu) Importance: Undecided Status: New ** Tags: vivid ** Attachment added: "Test puppet recipe that fails when executed on vivid using: 'puppet apply test.pp'" https://bugs.launchpad.net/bugs/1457957/+attachment/4402503/+files/test.pp ** Tags added: verification-done ** Tags removed: verification-done ** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4
If this can be fixed as I asked in comment #3, and the squidguard package is completely broken otherwise, then an update to 15.04 would be fine. Someone just needs to check this works, perform SRU verification, etc. We should also look to add a dep8 test to squidguard to verify it works against the squid package shipped correctly. Having such a test would have prevented releasing with this situation. > I would think that using Ubuntu Server as a web proxy would be a fairly common thing... I think squid use is quite common, but apparently not squidguard. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1448149 Title: Squid 3.3.8 incompatible with squidGuard 1.5-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1448149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4
Is there going to be some resolution to this or will we have to wait until 15.10?? Frankly, I find it bizarre that they're packaging an ancient version of squid3 with a bleeding-edge version of squidGuard. I would think that using Ubuntu Server as a web proxy would be a fairly common thing, and it's broken right from the start. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1448149 Title: Squid 3.3.8 incompatible with squidGuard 1.5-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1448149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1359143] Re: Upstream DNS should be determined by MAAS regiond package install script
** No longer affects: maas (Ubuntu) ** Changed in: maas Milestone: None => next ** Changed in: maas Importance: Medium => Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1359143 Title: Upstream DNS should be determined by MAAS regiond package install script To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1359143/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1443735] Re: recordfail false positive causes headless servers to hang on boot by default
This bug was fixed in the package grub2 - 2.02~beta2-23 --- grub2 (2.02~beta2-23) unstable; urgency=medium [ Debconf translations ] * [da] Danish (Joe Dalton; closes: #781333). [ Felix Zielcke ] * Run the tests with LC_MESSAGES=C.UTF-8. Some tests fail with non english locale. (Closes: #782580) [ Mathieu Trudel-Lapierre ] * Backport from upstream: - arp, icmp: Fix handling in case of oversized or invalid packets. (LP: #1428005) [ Robie Basak ] * Change the default GRUB_RECORDFAIL_TIMEOUT to 30, so interactive users still get the opporunity to intervene after a real boot failure, but headless users will not end up stuck after boot failures that were really power failures (closes: #782552, LP: #1443735). -- Colin Watson Thu, 14 May 2015 16:18:33 +0100 ** Changed in: grub2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1443735 Title: recordfail false positive causes headless servers to hang on boot by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1443735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457886] [NEW] Init program start with unknown arg splash
Public bug reported: Hi May bee on upstart splash arg have effect but on systemd not have this argument. $ ps -ax | grep init 1 ?Ss 0:06 /sbin/init splash $ stat /sbin/init File: ‘/sbin/init’ -> ‘/lib/systemd/systemd’ Size: 20 Blocks: 0 IO Block: 4096 symbolic link Device: fc00h/64512dInode: 3145794 Links: 1 Access: (0777/lrwxrwxrwx) Uid: (0/root) Gid: (0/root) Access: 2015-05-22 06:52:38.428851425 +0300 Modify: 2015-05-07 09:27:22.0 +0300 Change: 2015-05-17 12:02:14.191103891 +0300 Birth: - Please correct this. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: init 1.22ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: Unity Date: Fri May 22 16:21:23 2015 SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1457886 Title: Init program start with unknown arg splash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1457886/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457499] Re: MAAS UI showing Wily images as 'wily' instead of as '15.10'
** Changed in: maas Status: New => Invalid ** Changed in: maas (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1457499 Title: MAAS UI showing Wily images as 'wily' instead of as '15.10' To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1457499/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1456864] Re: package apache2 2.4.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1456864 Title: package apache2 2.4.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1456864/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1456864] Re: package apache2 2.4.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1456864 Title: package apache2 2.4.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1456864/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457753] Re: smbclient not installed by default 15.04 and newer
On Fri, May 22, 2015 at 10:59:44AM -, Gregor wrote: > The problem as i understand it was that Ubutnu is offering this feature > via GUI, but a component needed for the GUi in Ubuntu to work is > missing. Software is therefore not acting as expected or as indicated > that it is supposed to act. Therefore in my opinion it is a bug. That's fine, but then the bug is "GUI feature X is shipped by default but doesn't work by default", not "smbclient not installed by default". It could be fixed by adding smbclient as a dependency on the package that ships feature X. We can convert this bug and reopen it, but please provide details of feature X so that we can work on it on that basis. > The solution to that (and to keep it in line with Debian) would be to > offer the install of missing package when the user would try to perform > the desired action. That's another option. Please provide details of the problem itself, rather than pre-supposing a solution. Once you have provided these details, please change the bug status back to New. ** Changed in: samba (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1457753 Title: smbclient not installed by default 15.04 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1457753/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457753] Re: smbclient not installed by default 15.04 and newer
Then again, if we wanted Debian, we would just install Debian. The problem as i understand it was that Ubutnu is offering this feature via GUI, but a component needed for the GUi in Ubuntu to work is missing. Software is therefore not acting as expected or as indicated that it is supposed to act. Therefore in my opinion it is a bug. The solution to that (and to keep it in line with Debian) would be to offer the install of missing package when the user would try to perform the desired action. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1457753 Title: smbclient not installed by default 15.04 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1457753/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1335391] Re: etckeeper with git breaks update-manager
+1 for the "Please tell me who you are." issue, with Hungarian locale and bash. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1335391 Title: etckeeper with git breaks update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1335391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457753] Re: smbclient not installed by default 15.04 and newer
Thank you for taking the time to report this bug and helping to make Ubuntu better. Personally I don't mind either way. Users who need smbclient generally know they need it and so should be able to install it themselves. Changing this kind of default between releases isn't really a regression - the point of new releases is to be able to change defaults like this. If you really want this changed, first this needs to be checked on Debian to see if it is an Ubuntu-only issue or not. If this does turn out to apply to Debian too, then I think it is most likely a deliberate design decision and a justification to change it back would need to be made in Debian. I'll mark the Ubuntu task "Won't Fix" since: 1) I think it is most likely a deliberate change in Debian, therefore not a bug, and not something we'd consider changing directly in Ubuntu over Debian's decision without further justification; and 2) I think it's therefore unlikely that this change will ever happen in Ubuntu, there's little point in keeping a bug open about it, and keeping the bug open gives others misleading expectations. I would be happy for this bug to be re-opened though if any of my assumptions are wrong or if a real reason to change it comes to light. ** Changed in: samba (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1457753 Title: smbclient not installed by default 15.04 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1457753/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457754] Re: "E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1
It's not about the apt version. I just got it with the downgraded apt, and something apt does when installing the packages fixes it, since it started working once I re-installed the older packages... if you don't believe, here's a bit cut-off but copy-pasted output from my lxc: --- root@wily-gui:~# apt-get autoremove --purge unity.* Luetaan pakettiluetteloita... Valmis ... 0 päivitetty, 14 uutta asennusta, 106 poistettavaa ja 16 päivittämätöntä. Noudettavaa arkistoa 3 375 kt. Toiminnon jälkeen vapautuu 79,8 M t levytilaa. Haluatko jatkaa? [K/e] E: Method http has died unexpectedly! E: Aliprosessi http aiheutti suojausvirheen. root@wily-gui:~# apt-get autoremove --purge unity.* Luetaan pakettiluetteloita... Valmis ... 0 päivitetty, 14 uutta asennusta, 106 poistettavaa ja 16 päivittämätöntä. Noudettavaa arkistoa 3 375 kt. Toiminnon jälkeen vapautuu 79,8 M t levytilaa. Haluatko jatkaa? [K/e] k E: Method http has died unexpectedly! E: Aliprosessi http aiheutti suojausvirheen. root@wily-gui:/# dpkg -i libapt-* apt* (Reading database ... 118694 files and directories currently installed.) Preparing to unpack libapt-inst1.5_1.0.9.7ubuntu4_amd64.deb ... Unpacking libapt-inst1.5:amd64 (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Preparing to unpack libapt-pkg4.12_1.0.9.7ubuntu4_amd64.deb ... Unpacking libapt-pkg4.12:amd64 (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Preparing to unpack apt_1.0.9.7ubuntu4_amd64.deb ... Unpacking apt (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Preparing to unpack apt-utils_1.0.9.7ubuntu4_amd64.deb ... Unpacking apt-utils (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Setting up libapt-pkg4.12:amd64 (1.0.9.7ubuntu4) ... Setting up apt (1.0.9.7ubuntu4) ... Setting up libapt-inst1.5:amd64 (1.0.9.7ubuntu4) ... Setting up apt-utils (1.0.9.7ubuntu4) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... root@wily-gui:/# apt-get autoremove --purge unity.* Luetaan pakettiluetteloita... Valmis Muodostetaan riippuvuussuhteiden puu Luetaan tilatiedot... Valmis ... 0 päivitetty, 14 uutta asennusta, 106 poistettavaa ja 16 päivittämätöntä. Noudettavaa arkistoa 3 375 kt. Toiminnon jälkeen vapautuu 79,8 M t levytilaa. Haluatko jatkaa? [K/e] Nouda:1 http://archive.ubuntu.com/ubuntu/ wily/universe gnome-control-center amd64 1:3.14.2-2ubuntu3 [1 464 kB] Nouda:2 http://archive.ubuntu.com/ubuntu/ wily/main libcolord-gtk1 amd64 0.1.25-1.1build2 [16,7 kB] Nouda:3 http://archive.ubuntu.com/ubuntu/ wily/main libgnome-control-center1 amd64 1:3.14.2-2ubuntu3 [90,1 kB] ... ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some config according to https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in- + containers/ + https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged- containers/ + enabling network. --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1457754 Title: "E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1457754/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1457753] Re: smbclient not installed by default 15.04 and newer
I should make it clear that if Debian change it, then Ubuntu will likely follow. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1457753 Title: smbclient not installed by default 15.04 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1457753/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1447944] Re: Migration of custom configuration to my.cnf.migrated is not explicit enough
** Summary changed: - Cannot access mariadb after upgrading to Ubuntu 15.04: Plugin 'unix_socket' is not loaded + Migration of custom configuration to my.cnf.migrated is not explicit enough ** Changed in: mariadb-10.0 (Ubuntu) Status: Confirmed => Triaged ** Changed in: mariadb-10.0 (Ubuntu) Assignee: Otto Kekäläinen (otto) => Robie Basak (racb) ** Changed in: mariadb-10.0 (Ubuntu) Importance: Undecided => Medium ** Package changed: mariadb-10.0 (Ubuntu) => mysql-5.6 (Ubuntu) ** Tags added: mysql-5.6-transition -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1447944 Title: Migration of custom configuration to my.cnf.migrated is not explicit enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1447944/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1455818] Re: mysql-server-5.6.postrm fails when /usr/share/mysql-common/configure-symlinks doesn't exist
** Tags added: mysql-5.6-transition -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1455818 Title: mysql-server-5.6.postrm fails when /usr/share/mysql-common/configure- symlinks doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1455818/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1447944] [NEW] Migration of custom configuration to my.cnf.migrated is not explicit enough
You have been subscribed to a public bug: After upgrading from 14.10 to 15.04, I cannot access mariadb anymore on the local system. root@system:~# mysql -p Enter password: ERROR 1524 (HY000): Plugin 'unix_socket' is not loaded System is on Ubuntu 15.04 vivid, mariadb-server is mariadb-server: Installiert: 10.0.17-0ubuntu1 Installationskandidat: 10.0.17-0ubuntu1 ** Affects: mysql-5.6 (Ubuntu) Importance: Medium Assignee: Robie Basak (racb) Status: Triaged -- Migration of custom configuration to my.cnf.migrated is not explicit enough https://bugs.launchpad.net/bugs/1447944 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
