[Bug 1531801] Re: Please update to upstream major release 3
Debian maintainer has must uploaded to debian: ftpmaster just said: postfix_3.0.3-1_multi.changes uploaded successfully to localhost -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1531801 Title: Please update to upstream major release 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1531801/+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 1531801] Re: Please update to upstream major release 3
We just found and fixed the problem . -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1531801 Title: Please update to upstream major release 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1531801/+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 1531801] Re: Please update to upstream major release 3
I'm in contact with the debian maintainer. He's pretty close to uploading, there's just a single problem with the Makefile and it's generation of doc pages. So the debian version will be available soon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1531801 Title: Please update to upstream major release 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1531801/+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 1531801] [NEW] postfix outdated in 16.04
Public bug reported: Hi, the current 16.04 xenial alpha still comes with a postfix 2.11.3, while the current upstream stable release of postfix is 3.0. Since 16.04 is intended to be an LTS, it should not come with a major release that will soon not be supported anymore. regards ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1531801 Title: postfix outdated in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1531801/+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 1530233] [NEW] puppet outdated
Public bug reported: Hi, the current alpha of xenial 16.04 still comes with a puppet 3.8.4, but the current version of puppet is 4.3. Since 16.04 is supposed to be a LTS release, would be good to have a recent major version. regards Hadmut ** Affects: puppet (Ubuntu) Importance: Undecided Status: New -- 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/1530233 Title: puppet outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1530233/+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 1514080] [NEW] lxc-templates lacks template for ubuntu core
Public bug reported: Hi, lxc-templates comes with tamples for ubuntu and ubuntu-cloud, but both are rather large and „complete”, too large for most applications. E.g. it does not make sense to have multiple consoles running in a container or an sshd. Would be nice to have a template for ubuntu-core as an absolute minimal system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc-templates 1.1.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 7 16:04:54 2015 InstallationDate: Installed on 2015-10-08 (29 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug 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/1514080 Title: lxc-templates lacks template for ubuntu core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514080/+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 1514080] Re: lxc-templates lacks template for ubuntu core
As far as I can see the ubuntu template uses debootstrap and not the core image. And a plain lxc image created with the ubuntu template takes 379 MB (btrfs file system), while an unpacked ubuntu core has just 145 MB. So I doubt that this is the same. It is, btw., not a good idea to include vom and sshd by default. What would a lxc container need a sshd for by default? On the contrary, it is definitely a severe security problem to install an sshd on y machine , which has a default user ubuntu with default password ubuntu and ability to become root with the same default password. Who creates such security gaps? -- 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/1514080 Title: lxc-templates lacks template for ubuntu core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514080/+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 1507230] [NEW] 15.10beta trouble with suspend
Public bug reported: Hi, the powermode suspend (to ram) was working perfectly, reliably, fast and without any problem on my machine with 14.04. It does not work properly with 15.10 beta anymore: Doing a suspend through the Xubuntu menu drives the machine off. It can't restartet again and needs a fresh boot. using pm-suspend puts the machine in a correct suspend mode, where the power led is blinking as expected, and even wakes up again, but the screen is not initialized correctly. It looks pink, severely distorted, contents moving. I can see something which remotely looks like the login window, but need a full reboot in order to make the screen work again correctly. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 18 01:44:29 2015 InstallationDate: Installed on 2015-10-08 (9 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1507230 Title: 15.10beta trouble with suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1507230/+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] Re: puppet uses upstart for service status checks in vivid
I also ran into that problem on 15.10 beta. -- 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/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 1503674] [NEW] depends on iptables instead of nftables
Public bug reported: Hi, I had a fresh 15.10 beta install and have thrown out iptables in favour of nftables. Unfortunately, apt removed the docker.io package as well, since it depends on iptables. Shouldn't docker.io be able to deal solely with nftables without the need for iptables? regards ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: docker.io (not installed) ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Oct 7 14:11:26 2015 InstallationDate: Installed on 2015-09-03 (33 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1503674 Title: depends on iptables instead of nftables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1503674/+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 1467854] [NEW] python-vm-builder lacks btrfs file system support
Public bug reported: Hi, when installing Ubuntu from CD or through PXE you have the option of choosing btrfs as the filesystem (using subvolumes for / and /home). Would be nice if python-vm-builder would support the same, to allow realistic tests in virtual machines of machines to be installed on hardware regards Hadmut ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-vm-builder 0.12.4+bzr489-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 23 11:24:33 2015 PackageArchitecture: all SourcePackage: vm-builder UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1467854 Title: python-vm-builder lacks btrfs file system support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1467854/+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 1467882] [NEW] TypeError: 'NoneType' object has no attribute '__getitem__'
Public bug reported:
Hi,
vmbuilder crashes in afterbuild cleanup when doing
vmbuilder vbox ubuntu --suite trusty --flavour virtual \
--arch i386 --mem 1024 --rootsize 8000 \
--dest /tmp/ubuntu-base --name ubuntu-base \
--hostname ubuntu-base --user danisch --pass blabla \
--addpkg acpid --addpkg linux-image-generic
last messages are (full output attached)
2015-06-23 12:19:40,022 INFO:
2015-06-23 12:19:40,194 INFO: Searching for GRUB installation directory ...
found: /boot/grub
2015-06-23 12:19:40,245 INFO: Calling hook: install_kernel
2015-06-23 12:19:43,383 INFO: Calling hook: post_install
2015-06-23 12:19:43,385 INFO: Calling hook: unmount_partitions
2015-06-23 12:19:43,387 INFO: Unmounting target filesystem
2015-06-23 12:19:47,023 INFO: Calling hook: convert
2015-06-23 12:19:47,025 INFO: Converting /tmp/tmpR78GUJ to vdi, format
/tmp/ubuntu-base/tmpR78GUJ.vdi
2015-06-23 12:19:47,567 INFO: Converting from raw image
file=/tmp/tmpR78GUJ to file=/tmp/ubuntu-base/tmpR78GUJ.vdi...
2015-06-23 12:19:47,572 INFO: Creating dynamic image with size 9462349824
bytes (9024MB)...
2015-06-23 12:20:37,060 INFO: Calling hook: deploy
2015-06-23 12:20:37,249 INFO: Cleaning up
Traceback (most recent call last):
File /usr/bin/vmbuilder, line 24, in module
cli.main()
File /usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py, line 232,
in main
hypervisor.finalise(destdir)
File /usr/lib/python2.7/dist-packages/VMBuilder/hypervisor.py, line 79, in
finalise
self.call_hooks('deploy', destdir)
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 69, in
call_hooks
self.cleanup()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 44, in
cleanup
self._cleanup_cbs.pop(0)()
File /usr/lib/python2.7/dist-packages/VMBuilder/disk.py, line 129, in
lambda
self.vm.add_clean_cb(lambda : self.unmap(ignore_fail=True))
File /usr/lib/python2.7/dist-packages/VMBuilder/disk.py, line 194, in unmap
parted_oldmap=part.filename[len(/dev/mapper/):-1]+p+part.filename[-1]
TypeError: 'NoneType' object has no attribute '__getitem__'
regards
Hadmut
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-vm-builder 0.12.4+bzr489-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jun 23 12:22:13 2015
PackageArchitecture: all
SourcePackage: vm-builder
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: vm-builder (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1467882
Title:
TypeError: 'NoneType' object has no attribute '__getitem__'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1467882/+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 1467882] Re: TypeError: 'NoneType' object has no attribute '__getitem__'
** Attachment added: full output of command https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1467882/+attachment/4419280/+files/vmbuilder_output.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1467882 Title: TypeError: 'NoneType' object has no attribute '__getitem__' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1467882/+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 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 1429486] [NEW] docker.io too outdated, cannot interpret common Dockerfiles
Public bug reported: Hi, the docker.io version currently in trusty/14.04 seems to be too outdated, even if updated in trusty-updated. It cannot interpret clauses quite common in todays Dockerfiles. E.g. I tried to generate a Firefox sync server by building the Dockerfile coming with git clone https://github.com/mozilla-services/syncserver It fails, because this Dockerfile contains ADD Makefile *.ini *.wsgi *.rst *.txt *.py /home/app/syncserver/ which is not interpreted in the expected way. Instead, the first argument (the file Makefile) is copyied into the second argument, i.e. the file with the Name *.ini *.wsgi *.rst *.txt *.py /home/app/syncserver/ In other words: It does not expand whitespace or common wildcards, it just takes everything after the first whitespace as the second parameter, which clearly violates docker's manual. Upgrade recommended. regards Hadmut ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: docker.io 1.0.1~dfsg1-0ubuntu1~ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Mar 8 01:39:19 2015 InstallationDate: Installed on 2014-08-06 (213 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1429486 Title: docker.io too outdated, cannot interpret common Dockerfiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1429486/+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 1422162] [NEW] /usr/share/squid-deb-proxy-client/apt-avahi-discover crashing
Public bug reported: Hi, since recent upgrade /usr/share/squid-deb-proxy-client/apt-avahi- discover crashes (= uncaught exception): # /usr/share/squid-deb-proxy-client/apt-avahi-discover Traceback (most recent call last): File /usr/share/squid-deb-proxy-client/apt-avahi-discover, line 126, in module address = get_proxy_host_port_from_avahi() File /usr/share/squid-deb-proxy-client/apt-avahi-discover, line 109, in get_proxy_host_port_from_avahi hosts.append(AptAvahiClient(addr)) File /usr/share/squid-deb-proxy-client/apt-avahi-discover, line 44, in __init__ self.connect( (addr[0], addr[1], 0, 0) ) File /usr/lib/python2.7/asyncore.py, line 356, in connect raise socket.error(err, errorcode[err]) socket.error: [Errno 101] ENETUNREACH Reason: There's a problem with the avahi daemon running on the machine with squid proxy server. It always advertises an official IPv6 address, but its firewall allows a fe80:: address only, i.e. it advertieses an IPv6 address where the Port of the proxy is not available. While this is definitely a problem and misconfiguration of the proxy server, apt- avahi-discover should not crash, but simply not report that proxy server as found. regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: squid-deb-proxy-client 0.8.6 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 15 19:43:15 2015 PackageArchitecture: all SourcePackage: squid-deb-proxy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: squid-deb-proxy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1422162 Title: /usr/share/squid-deb-proxy-client/apt-avahi-discover crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1422162/+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 1405625] [NEW] Wrong indentation in multi-ressources with array
Public bug reported:
Hi,
the emacs mode generates wrong indentation if a ressource looks like
this:
augeas{
'/etc/default/keyboard':
incl= '/etc/default/keyboard' ,
lens= 'shellvars.lns',
changes = [
'set XKBMODEL pc105',
'set XKBLAYOUT de',
'set XKBVARIANT nodeadkeys',
'set XKBOPTIONS ctrl:nocaps',] ;
'/etc/default/console-setup':
incl= '/etc/default/console-setup' ,
...
The auto indentation after ]; is wrong, because the emacs lisp program
is prepared to understand ], but not ];
The semicolon must be put on a line on its own, which looks ugly.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: puppet-el 3.4.3-1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Dec 25 14:16:06 2014
Dependencies: emacsen-common 2.0.7
InstallationDate: Installed on 2014-08-06 (140 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64
(20140722.3)
PackageArchitecture: all
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/1405625
Title:
Wrong indentation in multi-ressources with array
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1405625/+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 1363980] [NEW] kadmin.local in wrong package
Public bug reported: Hi, in contrast to /usr/bin/kadmin, /usr/bin/kadmin.local does not use the server, but accesses the database directly. It does not use the krb5 -admin-server. It therefore should not be packed into the krb5-admin-server, but in the krb5-kdc package, to allow using it without/before installing the admin server. Doesn't make sense to put a program designed to be independent from admin-server in the package with admin-server. regards Hadmut ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: krb5-admin-server 1.12+dfsg-2ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Sep 1 14:18:26 2014 SourcePackage: krb5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: krb5 (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 krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1363980 Title: kadmin.local in wrong package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1363980/+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 1345165] [NEW] lens for squid.conf not working
Public bug reported: Hi, another problem with the squid lens: It does not detect acl clauses correctly. It just lists existing acls like acl manager proto cache_object acl localhost src 127.0.0.1/32 ::1 acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais as acl[1]/ = (none) acl[2]/ = (none) acl[3]/ = (none) acl[4]/ = (none) acl[5]/ = (none) acl[6]/ = (none) acl[7]/ = (none) acl[8]/ = (none) acl[9]/ = (none) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: augeas-tools 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jul 20 00:02:01 2014 SourcePackage: augeas UpgradeStatus: Upgraded to trusty on 2014-04-19 (91 days ago) ** Affects: augeas (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 augeas in Ubuntu. https://bugs.launchpad.net/bugs/1345165 Title: lens for squid.conf not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1345165/+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 1324685] Re: gem file access problem
btw. same problem for everything installed under /usr/local , such as /usr/local/bin/rake . Becomes root-owned but unreadable because of the umask. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ruby1.9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1324685 Title: gem file access problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby1.9.1/+bug/1324685/+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 1324685] Re: gem file access problem
I've found what causes the problem. /usr/bin/bundle doesn't set the umask, and instead uses the umask set by the user who calls it. In my case, my umask is 027. Therefore, all files created by bundle (through sudo) in /var/lib/gems become unreadable for users other than root, and therefore bundle will work for root only, unless a chmod -R a+rX /var/lib/gems is performed. Problem doesn't occur if I use a umask of 022 . So bundle needs to set it's umask properly, i.e. something like 022. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ruby1.9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1324685 Title: gem file access problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby1.9.1/+bug/1324685/+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 1322898] [NEW] squid lens fails with current squid syntax
Public bug reported: Hi, the squid lens that comes with augeas doesn't know all settings of the current squid version, and thus fails to read and to work on squid configs if those commands are used. I found the problem with cache_access_log cache_store_log If the config contains these statements, augeas/augtool fails to read the file. regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: augeas-lenses 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 24 21:33:37 2014 Dependencies: PackageArchitecture: all SourcePackage: augeas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: augeas (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 augeas in Ubuntu. https://bugs.launchpad.net/bugs/1322898 Title: squid lens fails with current squid syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1322898/+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 1310569] Re: Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
First news from the upstream bug: It seams as if the problem was not the file contents, but the file name, the second 'o' allegedly was a cyrillic o... *damned trap* -- 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/1310569 Title: Error: Could not set 'file' on ensure: invalid byte sequence in US- ASCII To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1310569/+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 1310569] [NEW] Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
Public bug reported: Hi, puppet fails to install file ressources from puppet:///... for some files with the error message Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII Wrapped exception: invalid byte sequence in US-ASCII Error: /Stage[main]/Hadmut::Application::X11_common/File[/usr/local/share/fonts/FreeFonts/Momоt___.ttf]/ensure: change from absent to file failed: Could not set 'file' on ensure: invalid byte sequence in US-ASCII because it does not open files in :binary mode. Just to have this bug known to ubuntu, I already have opened an upstream bug report more than a month ago, which unfortunately did not get any response yet: https://tickets.puppetlabs.com/browse/PUP-1890 regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: puppet (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 21 13:04:25 2014 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/1310569 Title: Error: Could not set 'file' on ensure: invalid byte sequence in US- ASCII To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1310569/+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 1310120] [NEW] wrong path in squid lens
Public bug reported: the squid lens (squid.aug) contains let filter = incl /etc/squid/squid.conf but trusty's squid.conf path is /etc/squid3/squid.conf augtool can't read /etc/squid3/squid.conf and that seems to be the reason. regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: augeas-lenses 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 20 00:30:26 2014 Dependencies: PackageArchitecture: all SourcePackage: augeas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: augeas (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 augeas in Ubuntu. https://bugs.launchpad.net/bugs/1310120 Title: wrong path in squid lens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1310120/+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 1309796] [NEW] wrong default augeas lenses path
Public bug reported:
the augeas resource does not work with current puppet and complains
„loading failed”
It works when the additional parameter
load_path = /usr/share/augeas/lenses/dist,
is given, but such details should usually be kept out of puppet
manifests for default lenses.
Reason:
It tries to find lenses under the path
/var/lib/puppet/lib/augeas/lenses
while unter ubuntu 14.04 the augeas lenses are located under
/usr/share/augeas/lenses/dist
The problem is in /usr/lib/ruby/vendor_ruby/puppet/provider/augeas/augeas.rb:
if Puppet::FileSystem::File.exist?(#{Puppet[:libdir]}/augeas/lenses)
load_path #{Puppet[:libdir]}/augeas/lenses
end
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: puppet (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Apr 19 01:20:03 2014
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/1309796
Title:
wrong default augeas lenses path
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1309796/+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 1296681] Re: failed to change apparmor profile to lxc-container-default
It fails. I would say the problem is that /etc/apparmor.d/lxc/lxc-default includes a file named lxc-container-default which simply is missing in the package and thus can't be included. # /etc/init.d/apparmor reload * Reloading AppArmor profiles Enocoding of mount rule failed ERROR processing policydb rules for profile lxc-container-default, failed to load Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd # lxc-start -n meinerster lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: No such file or directory - failed to change apparmor profile to lxc-container-default lxc-start: invalid sequence number 1. expected 4 lxc-start: failed to spawn 'meinerster' lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/perf_event/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/devices/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/memory/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuacct/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu/lxc/meinerster lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/lxc/meinerster -- 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/1296681 Title: failed to change apparmor profile to lxc-container-default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1296681/+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 1296681] [NEW] failed to change apparmor profile to lxc-container-default
Public bug reported: Hi, I've recently upgraded my machine to 14.04 beta and tried lxc. Worked just fine (about 10 days ago). After some daily updates of the machine I wanted to use lxc again, but now I am running into this problem (the files in the cgroup_rmdir lines haven sequence numbers like -1, -2, -3, -4,...) # lxc-start -n meinerster lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: No such file or directory - failed to change apparmor profile to lxc-container-default lxc-start: invalid sequence number 1. expected 4 lxc-start: failed to spawn 'meinerster' lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/perf_event/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/devices/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/memory/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuacct/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu/lxc/meinerster-4 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/lxc/meinerster-4 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 24 13:02:58 2014 InstallationDate: Installed on 2013-04-29 (328 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2014-03-05 (19 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1296681 Title: failed to change apparmor profile to lxc-container-default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1296681/+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 1296681] Re: failed to change apparmor profile to lxc-container-default
uncommenting lxc.aa_profile = unconfined in the config made the machine run again, but still spit out error messages. -- 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/1296681 Title: failed to change apparmor profile to lxc-container-default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1296681/+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 1286196] Re: puppet package ensure absent/purged causes warnings
Looks good. :-) Thanks! -- 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/1286196 Title: puppet package ensure absent/purged causes warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1286196/+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 1290334] [NEW] augtool does not properly parse /etc/cups/*.conf
Public bug reported: Hi, augtool has lenses intended to parse /etc/cups/*.conf, which do not work as expected. Do a augtool print /files/etc/cups/cupsd.conf It presents directives as /files/etc/cups/cupsd.conf/directive[4] = Listen /files/etc/cups/cupsd.conf/directive[4]/arg = localhost:631 which makes it difficult to automatically change data. Usually augtool should give something like .../cupsd.conf/Listen[0]... regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: augeas-tools 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 10 13:07:21 2014 InstallationDate: Installed on 2013-04-29 (314 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) SourcePackage: augeas UpgradeStatus: Upgraded to trusty on 2014-03-05 (5 days ago) ** Affects: augeas (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 augeas in Ubuntu. https://bugs.launchpad.net/bugs/1290334 Title: augtool does not properly parse /etc/cups/*.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1290334/+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 1286196] [NEW] puppet incompatible with 14.04 packet mechanism
Public bug reported: Hi, I just tried to configure a 14.04 machine with puppet. puppet reports lots of error messages like Warning: Failed to match dpkg-query line dpkg-query: Kein Paket gefunden, das auf rxp passt\n saying that it could find and install a package rxp (or other packages), although it actually did install that package. For some reason puppet installs the package and then reports that it could not find and install it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: puppet (not installed) ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5 Uname: Linux 3.13.0-13-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Fri Feb 28 16:46:40 2014 ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash 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/1286196 Title: puppet incompatible with 14.04 packet mechanism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1286196/+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 1246229] Re: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ...
I've found a reason on the first machine. Since I use parameterized classes, puppet did not work without hiera (complains), although I had not used it. Since puppet with hiera complains about a missing /etc/puppet/hiera.yaml, I've made an empty one. That's the problem. Just writing --- into it solves the problem. Now I have to check why I got the same error on the second machine... -- 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/1246229 Title: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1246229/+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 1246229] Re: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ...
I'v copied your testcase with copy and paste to /etc/puppet/manifests/test.pp and run: # puppet apply /etc/puppet/manifests/test.pp Could not retrieve zpool_version: undefined method `captures' for nil:NilClass Warning: Could not retrieve fact fqdn Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at /etc/puppet/manifests/test.pp:5 on node pcdanisch Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at /etc/puppet/manifests/test.pp:5 on node pcdanisch Since this is a ruby error message, I've checked which ruby version puppet runs: /usr/bin/ruby - /etc/alternatives/ruby - /usr/bin/ruby1.9.1 Same with another machine that has been installed as 13.04 and upgraded to 13.10. I don't have a freshly installed machine here right now, I have to get at home to do so. regards -- 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/1246229 Title: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1246229/+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 1246229] Re: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ...
And, btw., ruby-hiera was installed on the first, but not on the second machine. Both behave identically. -- 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/1246229 Title: Error: Puppet::Parser::AST::Resource failed with error TypeError: no implicit conversion from nil to integer at ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1246229/+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 888552] [NEW] cyrus-sasl2 denies authentication if host name unresolvable
Public bug reported: This just cost me about 5 hours of debugging. cyrus-sasl2 does not authenticate against a server if the hostname is not dns-resolvable. After upgrading to oneirc, I wondered, why the mail client mutt could access an imap server on three on my systems, but not on the fourth machine. It did not even try to authenticate after the imap server's greeting message and aborted with Error allocating SASL connection , although the configuration files were identical. After hours of debugging and analyzing with strace, tcpdump and source code I found that the reason was that the machine where it did not work was not known to my DNS name server. A query to it's (plain) hostname therefore failed. After modifying DNS to give an answer, SASL worked. Before, sasl_client_new() just gave a -1 as a result code. This is broken by design. I did not even work if the server was at 127.0.0.1, and the machine and the authentication should really work even without DNS resolving. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libsasl2-2 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Thu Nov 10 14:39:23 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: cyrus-sasl2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/888552 Title: cyrus-sasl2 denies authentication if host name unresolvable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/888552/+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 888552] Re: cyrus-sasl2 denies authentication if host name unresolvable
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/888552 Title: cyrus-sasl2 denies authentication if host name unresolvable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/888552/+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 886770] Re: Directory /var/log/libvirt/qemu missing in package
% dpkg -l | grep libvirt rc libvirt-bin 0.8.8-1ubuntu6.6 the programs for the libvirt library ii libvirt0 0.9.2-4ubuntu15.1 library for interfacing with different virtualization systems ii libvirtodbc0 6.1.3+dfsg1-1ubuntu1 high-performance database - ODBC libraries ii python-libvirt0.9.2-4ubuntu15.1 % cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.10 DISTRIB_CODENAME=oneiric DISTRIB_DESCRIPTION=Ubuntu 11.10 I've installed the package - don't know - about 1-2 years ago. recently upgraded to oneiric. I currently do not see how libvirt-bin could create that directory during install, because there is no postinst script. Just a .postrm . (The upgrade-procedure failed and aborted, because the package downloading the flash plugin for the browser tried to download the flash plugin at a system state where the network configuration was down and exited with a exit value 0. Thus the upgrader natty-oneiric aborted. I then had to finish things manually. Maybe this has influenced things somehow. (but all packages were definitely configured.)) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/886770 Title: Directory /var/log/libvirt/qemu missing in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/886770/+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 886770] Re: Directory /var/log/libvirt/qemu missing in package
Oh, yep, the package was actually deinstalled, but not purged. Didn't notice that, must have been removed somewhere in the broken upgrade process. Thus the directory was gone, while /var/log/libvirt and /var/log/libvirt/shutdownlog.log remained on the system, as well as /etc/logrotate.d/libvirtd (and probably all other files in /etc). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/886770 Title: Directory /var/log/libvirt/qemu missing in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/886770/+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 886770] Re: Directory /var/log/libvirt/qemu missing in package
Please do. I'll just purge the package. thanks and regards -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/886770 Title: Directory /var/log/libvirt/qemu missing in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/886770/+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 886770] [NEW] Directory /var/log/libvirt/qemu missing in package
Public bug reported: Hi, libvirt-bin comes with a /etc/logrotate.d/libvirtd that tries to logrotate log files in /var/log/libvirt/qemu , but the libvirt-bin package contains only /var/log/libvirt and not /var/log/libvirt/qemu. If that directory is absent (i.e. when not made manually), the logrotate cronjob generates an error message at every run: /etc/cron.daily/logrotate: error: error accessing /var/log/libvirt/qemu: No such file or directory error: libvirtd:1 glob failed for /var/log/libvirt/qemu/*.log error: found error in /var/log/libvirt/qemu/*.log , skipping If a logrotate accesses a directory, this directory must exist. Therefore, please add that directory to the package (even if empty) to avoid thus error messages. It is not just an error message. It is an error. regards ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libvirt-bin (not installed) ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Nov 6 10:25:41 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) ProcEnviron: LANGUAGE=en_US:de_DE:en PATH=(custom, user) LANG=de_DE.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: libvirt UpgradeStatus: Upgraded to oneiric on 2011-10-29 (7 days ago) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/886770 Title: Directory /var/log/libvirt/qemu missing in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/886770/+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 613619] Re: qemu-kvm misinterprets LVM volume geometry
Serge, sorry, can't tell. I did not install any new virtual machine for some time. The existing ones are running reliably (see above). So I actually don't know whether this problem still exists. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/613619 Title: qemu-kvm misinterprets LVM volume geometry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/613619/+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 613619] Re: qem/kvm misinterprets LVM volume geometry
Here are some discussions where I found problems mentioned that seem to be the same or closely related problem: http://www.howtoforge.com/forums/archive/index.php/t-30329.html http://ubuntuforums.org/showthread.php?t=1425421 I am not sure yet what exactly the reason is, but I experienced similar problems on several hosts, both with kvm and qemu. You can install a system on a partitioned lvm volume from the host, but once you boot it, the virtual machine can't mount it (or generates rubbish like reading files that have been deleted under FAT16). Interestingly one of the commenters in the ubuntu discussion above mentioned that it worked when leaving space at the beginning of the lvm. I once tried to convert a regular ubuntu machine into an almost identical virtual copy for backup reasons. I first used fdisk -c with -u command (which results in different positions for the partitions), and when I bootet that virtual machine, it could mount only the first two partitions, but then ran into severe trouble when trying to mount the third filesystem (beeing unable to display file permissions or contents and such things). When I repeated everything with a regular old- fashioned fdisk (without -c and -u) it worked. But that was obviously some luck, since repeating this with lvm volumes of different size was not possible. For some reason the virtual disk looks somehow different from inside (virtual machine) than from outside (host), and it might be related to the the beginning of the lvm volume. -- qem/kvm misinterprets LVM volume geometry https://bugs.launchpad.net/bugs/613619 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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
[Bug 613619] [NEW] qem/kvm misinterprets LVM volume geometry
Public bug reported: Binary package hint: qemu-kvm Hi, when running qemu/kvm with kvm logical volumes as virtual disks, there's a severe problem, maybe with disk geometry. When partitioning the lvm volume with fdisk or parted, generating the partition device entries with kpartx, creating filesystems (ext3, fat16,..) and installing a linux with debootstrap, there's quite often the problem that the virtual machine then has problems accessing the virtual disk, resulting in read errors (usually misinterpreting dos filesystems, beeing unable to mount or fsck an ext3 and so on). Looks like the same problem as reported on http://qemu- forum.ipi.fi/viewtopic.php?f=4t=5218 Sometimes the problem did not occur when I use fdisk in dos compatibilty mode and/or rebooting the host after creating the partition table. Maybe that's a problem of disk geometry. Linux does not maintain a disk geometry for LVM volumes, so most tools like partition and filesystem generation tools use a default geometry of 255 heads and 63 sectors. On the other hand, the -drive option of qemu/kvm does not accept this geometry. The number of heads seems to be limited to 16. This is a severe problem since it can crash virtual machines and destroy data. regards ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: qemu (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Wed Aug 4 22:21:59 2010 KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD MachineType: TOSHIBA Satellite L300 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=/dev/mapper/nord-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/tcsh SourcePackage: qemu-kvm dmi.bios.date: 03/19/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd03/19/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-02T01XGR:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-02T01XGR dmi.sys.vendor: TOSHIBA ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- qem/kvm misinterprets LVM volume geometry https://bugs.launchpad.net/bugs/613619 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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
[Bug 613619] Re: qem/kvm misinterprets LVM volume geometry
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/53063840/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/53063841/CurrentDmesg.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/53063842/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/53063843/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/53063844/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/53063845/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/53063846/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/53063847/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/53063848/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/53063849/UdevLog.txt -- qem/kvm misinterprets LVM volume geometry https://bugs.launchpad.net/bugs/613619 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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
[Bug 610768] [NEW] does not install into given block devices
Public bug reported: Hi, I'm trying (and still doing some tests) to install a KVM host into a given lvm partition. When trying this, ubuntu-vm-builder completely ignored the block device (given with --raw) and created a qcow2. I am currently repeating tests, and although an existing block device as a hard disk is given, ubuntu-vm-builder still creates a directory in /tmp to run debootstrap on. This indicates a broken abstraction and object-orientation of the Disk model used in the vm builder. Please fix. A better concept would be to have an abstract base class of a Disk and then different inheritances for several disk types, which behave differently, e.g. for a given raw device use kpartx to create partitions and install directly into the partitions, while using a tmp file and qemu-img to pack a qcow2 image. But the current structure of vm-builder is poor in behalf of it's disk treatment. Definitely needs improvement urgently. regards ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ubuntu-vm-builder 0.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Jul 28 10:12:10 2010 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/usr/bin/tcsh SourcePackage: vm-builder ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- does not install into given block devices https://bugs.launchpad.net/bugs/610768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder 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
[Bug 610768] Re: does not install into given block devices
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/52625556/Dependencies.txt -- does not install into given block devices https://bugs.launchpad.net/bugs/610768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder 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
[Bug 582376] Re: Samba (nmbd) fails to start at boot
I'm coming from bug #590862 which was marked as a duplicate of this bug. And I had been asked to outline my network configuration. No, there is no error message in nmbd.log at all. The reason for not starting is not a failure in configuration. It always starts properly when I launch it manually with service nmbd start. On that machine I am using just a static ethernet network configuration. I'll attach my /etc/network/interfaces file. As far as I can see the problem is that nmbd is simply not always started at boottime. Interestingly I found it to be running in rare cases. My guess is that there is a timing problem with the net-device-up signal. The major problem might be the lack of proper documentation for the upstart code (and an increasing ignorance of the upstart maintainers). -- Samba (nmbd) fails to start at boot https://bugs.launchpad.net/bugs/582376 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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
[Bug 590862] [NEW] nmbd not started at boot time
Public bug reported: Binary package hint: samba Hi, nmbd does not start at boot time. I have to launch it with service nmbd start manually. (I'm using /etc/network/interfaces to configure my network). ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: samba 2:3.4.7~dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 BothFailedConnect: Yes Date: Mon Jun 7 18:35:14 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/tcsh SambaServerRegression: Yes SourcePackage: samba ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- nmbd not started at boot time https://bugs.launchpad.net/bugs/590862 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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
[Bug 590862] Re: nmbd not started at boot time
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49827164/Dependencies.txt ** Attachment added: SambaInstalledVersions.txt http://launchpadlibrarian.net/49827165/SambaInstalledVersions.txt -- nmbd not started at boot time https://bugs.launchpad.net/bugs/590862 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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
[Bug 357998] Re: openssh-client (amd64) can't login after upgrade to jaunty
ok, is attached. btw, the ssh login fails even if I try login to localhost, i.e. to the ubuntu machine itself. I had an RSA key only, the one that failed ufter upgrade. I could workaround by generating an dsa key, which works. Might be related to debian bug #357998 I am not really sure whether this really caused by the AMD64 architecture, it could also be a property of the rsa key, which causes trouble. regards ** Attachment added: ssh -vvv output http://launchpadlibrarian.net/25080582/ssh-vvv -- openssh-client (amd64) can't login after upgrade to jaunty https://bugs.launchpad.net/bugs/357998 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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
[Bug 274178] [NEW] dhcp3-client can't set IP address due to insufficient rights
Public bug reported: Binary package hint: dhcp3-client Hi, strange problem: On my notebook computer with WLAN I can't get DHCP addresses. Trace of the problem: dhclient3 properly receives an IP address from the server. dhclient3 then calls /sbin/dhclient-script to actually perform the configuration, e.g. use ifconfig to put the IP address received from the server on the interface, something like ifconfig wlan0 inet 1.2.3.4 netmask 255.255.255.0 broadcast 1.2.3.255 which fails. A trace showed that it fails with PERMISSION DENIED because of insufficient rights. dhclient3 performs a setuid and setgid to the user and group dhcp before calling the script /sbin/dhclient-script. Since this script is then run without root privileges, the ifconfig fails with EPERM. How was this intended to work? regards Hadmut ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhcp3-client can't set IP address due to insufficient rights https://bugs.launchpad.net/bugs/274178 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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
