[Bug 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
This bug was fixed in the package upstart - 1.4-0ubuntu7 --- upstart (1.4-0ubuntu7) precise; urgency=low * debian/manpages/upstart-events.7: Added missing events 'container' and 'not-container'. * Update 'runlevel' event emission time in upstart-events(7) (LP: #921501). * Merge of important upstream log fixes to avoid spinning when a job which leaks fds (such as 'sshd -D') is stopped (LP: #926468). * Merge of lp:~jamesodhunt/upstart/early-job-log-flush to allow jobs that _end_ very early in the boot to have their output logged. * debian/conf/flush-early-job-log.conf: Upstart job to force flushing of early job log output data when disk becomes writeable. * Re-enable job logging by default. [ Steve Langasek ] * init/tests/test_job_process.c: close all fds before running tests that check for unexpected open fds, so that files leaked from the environment don't cause the test suite to fail gratuitously. LP: #926473. * bump debhelper compat to 9 and adjust debian/rules to use the dpkg-buildflags interfaces, so that upstart can be cross-compiled and also so we pick up any future hardening flags for free. -- Steve Langasek steve.langa...@ubuntu.com Thu, 16 Feb 2012 07:52:11 + ** Changed in: upstart (Ubuntu Precise) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/926468/+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 929888] Re: ldap_result returns -1 when called from sssd
Upstream bug at http://www.openldap.org/its/index.cgi?findid=7167 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/929888 Title: ldap_result returns -1 when called from sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/+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 929888] Re: ldap_result returns -1 when called from sssd
Ryan, can you build openldap with the proposed patch and test? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/929888 Title: ldap_result returns -1 when called from sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/+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 875262] Re: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/sqlite.so'
** Bug watch added: Debian Bug tracker #656495 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656495 ** Also affects: php5 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656495 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/875262 Title: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/sqlite.so' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/875262/+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 929888] Re: ldap_result returns -1 when called from sssd
Built it myself (64bit) and put it here: http://kernel.ubuntu.com/~tjaalton/lp929888 install the lib and test. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/929888 Title: ldap_result returns -1 when called from sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/+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 925513] Re: plymouth should not run in container
@Serge, Could you explain why use of --path can lead to X crashing where lxc-create without --path is not? My motivation was: I don't want lxc-create to create the rootfs under /var/lib/lxc. I need the stuff to be stored elsewhere. I thought that the --path option in the template was made exactly for this purpose. Also notice that --path is specified as parameter for the ubuntu template and not for the lxc-create command: it is specified after -- in the command line. So I think it is really the plymouthd doing something with my framebuffer (which I assume my X server is also using), somehow eventually killing my X session. Does that make sense? I just noticed that I should probably have called lxc-ubuntu with the --trim option. The description of the option is somewhat misleading: Looking at the trim() function in the script itself, it in particular disables a couple of upstart services: quoting from the script: ~~ chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls u*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls tty[2-9].conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls plymouth*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls hwclock*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls module*.conf); do mv $f $f.orig; done' ~~ This also explains why another container (lucid) that was created with the --trim option works without problems. I will re-test the oneiric container with --trim... Cheers - Michael -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 903752] Re: [MIR] sssd
yeah adding a profile for apparmor is a good idea, I'll add a bug about it. -- 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/903752 Title: [MIR] sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ding-libs/+bug/903752/+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 875262] Re: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/sqlite.so'
** Changed in: php5 (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/875262 Title: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/sqlite.so' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/875262/+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 925513] Re: plymouth should not run in container
Confirmed: running the same lxc-create command with --trim creates a directly usable container. -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 929888] Re: ldap_result returns -1 when called from sssd
scratch that, it was tested elsewhere and didn't help :/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/929888 Title: ldap_result returns -1 when called from sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/+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 932239] Re: Multiple Samba security vulnerabilities
** This bug has been flagged as a security vulnerability -- 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/932239 Title: Multiple Samba security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/932239/+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 931236] Re: keystone install is unnecessarily interactive
** Changed in: keystone (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/931236 Title: keystone install is unnecessarily interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/931236/+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 933483] [NEW] --manifest option crashes vmbuilder
Public bug reported:
The help output as printed by `sudo vmbuilder kvm ubuntu --help`
explains the `--manifest` option.
--manifest=PATH If passed, a manifest will be written to PATH
If I use the option or include it in a configuration file, I get the
following output:
2012-02-16 15:44:19,412 INFO: Calling hook: preflight_check
2012-02-16 15:44:19,414 INFO: Calling hook: set_defaults
2012-02-16 15:44:19,415 INFO: Calling hook: bootstrap
2012-02-16 15:48:24,507 INFO: Calling hook: configure_os
2012-02-16 15:49:12,302 INFO: Updating certificates in /etc/ssl/certs...
WARNING: Skipping duplicate certificate cert_igca_rsa.pem
2012-02-16 15:49:12,315 INFO: WARNING: Skipping duplicate certificate
cert_igca_rsa.pem
2012-02-16 15:49:13,622 INFO: 156 added, 0 removed; done.
2012-02-16 15:49:13,626 INFO: Running hooks in
/etc/ca-certificates/update.ddone.
2012-02-16 15:49:18,398 INFO: Creating SSH2 RSA key; this may take some
time ...
2012-02-16 15:49:18,474 INFO: Creating SSH2 DSA key; this may take some
time ...
2012-02-16 15:49:18,489 INFO: Creating SSH2 ECDSA key; this may take some
time ...
2012-02-16 15:49:19,312 INFO: invoke-rc.d: policy-rc.d denied execution of
stop.
2012-02-16 15:49:19,315 INFO:
2012-02-16 15:49:19,315 INFO: Warning: Fake initctl called, doing nothing
2012-02-16 15:49:19,317 INFO:
2012-02-16 15:49:19,317 INFO: Warning: Fake initctl called, doing nothing
2012-02-16 15:49:28,549 INFO:
2012-02-16 15:49:28,550 INFO: Current default time zone: 'Europe/Helsinki'
2012-02-16 15:49:28,556 INFO: Local time is now: Thu Feb 16 15:49:28
EET 2012.
2012-02-16 15:49:28,557 INFO: Universal Time is now: Thu Feb 16 13:49:28
UTC 2012.
2012-02-16 15:49:28,557 INFO:
2012-02-16 15:49:49,920 INFO:
2012-02-16 15:49:49,921 INFO: Current default time zone: 'Europe/Helsinki'
2012-02-16 15:49:49,925 INFO: Local time is now: Thu Feb 16 15:49:49
EET 2012.
2012-02-16 15:49:49,925 INFO: Universal Time is now: Thu Feb 16 13:49:49
UTC 2012.
2012-02-16 15:49:49,925 INFO: Run 'dpkg-reconfigure tzdata' if you wish to
change it.
2012-02-16 15:49:49,926 INFO:
2012-02-16 15:50:11,689 INFO: restart: Unknown instance:
2012-02-16 15:50:15,961 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 216,
in main
distro.build_chroot()
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 84, in
build_chroot
self.call_hooks('configure_os')
File /usr/lib/python2.7/dist-packages/VMBuilder/distro.py, line 67, in
call_hooks
call_hooks(self, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/VMBuilder/util.py, line 165, in
call_hooks
getattr(context, func, log_no_such_method)(*args, **kwargs)
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/distro.py,
line 157, in configure_os
self.suite.create_manifest()
File /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/dapper.py,
line 72, in create_manifest
self.call_hook('fix_ownership', manifest)
AttributeError: 'Oneiric' object has no attribute 'call_hook'
Indeed, if I search for a definition for the `call_hook` method, there
are none:
ack-grep --python def\s+call_hook\s*\(
/usr/share/pyshared/VMBuilder/
Instead, there are four instances of `call_hooks`:
ack-grep --python def\s+call_hooks\s*\( /usr/share/pyshared/VMBuilder/
/usr/share/pyshared/VMBuilder/distro.py
65:def call_hooks(self, *args, **kwargs):
/usr/share/pyshared/VMBuilder/vm.py
130:def call_hooks(self, func):
/usr/share/pyshared/VMBuilder/plugins/__init__.py
88:def call_hooks(self, *args, **kwargs):
/usr/share/pyshared/VMBuilder/util.py
153:def call_hooks(context, func, *args, **kwargs):
This is Linux Mint 12 with python-vm-builder 0.12.4+bzr469-0ubuntu1 from
the Oneiric apt repository:
$ apt-cache policy python-vm-builder
python-vm-builder:
Installed: 0.12.4+bzr469-0ubuntu1
Candidate: 0.12.4+bzr469-0ubuntu1
Version table:
*** 0.12.4+bzr469-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
100 /var/lib/dpkg/status
$ dpkg -s python-vm-builder
Package: python-vm-builder
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 4840
Maintainer: Soren Hansen so...@ubuntu.com
Architecture: all
Source: vm-builder
Version: 0.12.4+bzr469-0ubuntu1
Depends: python (= 2.5), python-central (= 0.6.11), qemu-kvm |
qemu-kvm-extras, debootstrap (= 1.0.9), parted, kpartx, ubuntu-keyring,
python-cheetah, rsync
Recommends: python-libvirt, devscripts
** Affects: vm-builder (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder
[Bug 933480] [NEW] Picks hmac-md5 over hmac-sha1
Public bug reported: The OpenSSH client defaults to picking hmac-md5, which is based on the demonstrably insecure MD5 algorithm: faux@wilf:~% ssh -v localhost true 21 | grep hmac debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none MD5 has had practical vulnerabilities for around eight years, and its use is highly discouraged. SHA1 is a supported alternative, and is supported by the packaged openssh-server, and many other ssh implementations. MD5 is selected as man ssh_config suggests the default algorithms are, in order of preference (most preferred first): hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 Please append: MACs hmac-sha1,hmac-md5,umac...@openssh.com,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 ...to /etc/ssh/ssh_config, such that the client will prefer SHA-1: faux@wilf:~% ssh -v localhost true 21 | grep hmac debug1: kex: server-client aes128-ctr hmac-sha1 none debug1: kex: client-server aes128-ctr hmac-sha1 none This should have no compatibility concerns as MD5 is still a supported algorithm. Note that non-privileged users can override this setting either way on a per-connection basis by specifying MACs in ~/.ssh/config. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: openssh-client 1:5.8p1-7ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CheckboxSubmission: b0d31efda01870980e2e5a89390b685c CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d Date: Thu Feb 16 13:59:43 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:5.8p1-7ubuntu1 SSHClientVersion: OpenSSH_5.8p1 Debian-7ubuntu1, OpenSSL 1.0.0e 6 Sep 2011 SourcePackage: openssh UpgradeStatus: Upgraded to oneiric on 2011-05-03 (289 days ago) modified.conffile..etc.ssh.ssh.config: [modified] mtime.conffile..etc.ssh.ssh.config: 2012-02-16T13:59:11.376423 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/933480 Title: Picks hmac-md5 over hmac-sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/933480/+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 933480] Re: Picks hmac-md5 over hmac-sha1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/933480 Title: Picks hmac-md5 over hmac-sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/933480/+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
Re: [Bug 925513] Re: plymouth should not run in container
Quoting Michael Adam (ob...@samba.org): @Serge, Could you explain why use of --path can lead to X crashing where lxc-create without --path is not? After creating such a container, look at /var/lib/lxc/container/config and provided-path/config. My motivation was: I don't want lxc-create to create the rootfs under /var/lib/lxc. I need the stuff to be stored elsewhere. The recommended way (which will be in the server guide once written, before release) is to either symlink or bind mount the desired location under /var/lib/lxc. I thought that the --path option in the template was made exactly for this purpose. You're not the only one. This just came up on the lxc-users mailing list, which is why it stood out to me. Also notice that --path is specified as parameter for the ubuntu template and not for the lxc-create command: it is specified after -- in the command line. So I think it is really the plymouthd doing something with my framebuffer (which I assume my X server is also using), somehow eventually killing my X session. Does that make sense? I believe it's involved, but that it wouldn't happen if you didn't use --path. I just noticed that I should probably have called lxc-ubuntu with the --trim option. The description of the option is somewhat misleading: That'll accomplish the same thing in that plymouth won't run :) Looking at the trim() function in the script itself, it in particular disables a couple of upstart services: quoting from the script: ~~ chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls u*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls tty[2-9].conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls plymouth*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls hwclock*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls module*.conf); do mv $f $f.orig; done' ~~ This also explains why another container (lucid) that was created with the --trim option works without problems. I will re-test the oneiric container with --trim... Still, the moral of the story which we both agree on is: plymouth can be dangerous in containers :) -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 931236] Re: keystone install is unnecessarily interactive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: keystone (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/931236 Title: keystone install is unnecessarily interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/931236/+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 925513] Re: plymouth should not run in container
@Michael (and @Steve) So plymouth must do stuff over netlink. Instead of using --trim, you can simply add the lines from /etc/lxc/lxc.conf to the config file in your custom path. By not having those lines, you are telling lxc not to create a new network namespace. That means the container is running plymouth in the host's network namespace, and talking to the host's upstart over dbus over unix sockets, for instance. -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 925513] Re: plymouth should not run in container
Sorry, I said netlink, but a unix socket is more likely. same root cause -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 925513] Re: plymouth should not run in container
@Serge, thanks for your comments. I have experimented a little more. And I found that --path is indead at the very least misleading: If I don't use --path, then the config (snippet) given to lxc-create by -f is merged with the config that the template creates. If i do use paht, then the -f file is put under /var/lib/lxc while the template creates is stored under the --path. So at least this is bad and confusing. I also came up with the idea of linking or bind-mounting /var/lib/lxc to some other place. It seems safer ... :-) As for plymouth: I still have to experiment whether the behaviour is different when not using --path. But one of the main purposes for me to use is to get network virtualization, so it is not an option to _not_ configure network for my containers. :-) I usually use veth and one of the bridge devices created by libvirt. Cheers - Michael -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 892892] Re: mountall upgrade fails to install within lucid lxc container
The remaining part of the fix appears to be to remove lxcguest manually from your existing lxc guest. -- 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/892892 Title: mountall upgrade fails to install within lucid lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/892892/+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 925513] Re: plymouth should not run in container
@Steve, regarding whether disabling plymouth is the right fix: I don't know the mechanisms plymouth uses. 1. for system log entries, the right fix will be a syslog namespace, which doesn't yet exist. 2. if it uses proc files, we may be able to use apparmor to protect from plymouth, though that may make plymouth fail and cause the container to not boot right. The right fix would be a mix of user namespaces and proc file access filtering. 3. if it uses devices (ioctls or writes), we may be able to use apparmor and/or the devices namespace to protect from plymouth, but a device namespace will be the right fix. -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 892892] Re: mountall upgrade fails to install within lucid lxc container
The new upstart conflicts with lxcguest, so lxcguest is automatically removed from the Precise containers. -- 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/892892 Title: mountall upgrade fails to install within lucid lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/892892/+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 925513] Re: plymouth should not run in container
@Serge, I might have misready your statement about network config. I do add nettwork config (veth0, dev=virbr0, etc) manually. There is no /etc/lxc/lxc.conf in my system. The reason I used a config file snipped for lxc-create was exactly to get this network virtualization layer into the container config. Cheers - Michael -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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
Re: [Bug 925513] Re: plymouth should not run in container
Quoting Michael Adam (ob...@samba.org): @Serge, I might have misready your statement about network config. I do add nettwork config (veth0, dev=virbr0, etc) manually. What do you mean by adding it manually? Have you added it to the /data/lxc/ubuntu1/config? If there is no 'lxc.network.link' entry there, then a new network namespace is not created, which is what you need You should jsut be able to cat ./ubuntu1-template.con /data/lxc/ubuntu1/config to get something that works. There is no /etc/lxc/lxc.conf in my system. Ah, right, that was introduced with precise. The reason I used a config file snipped for lxc-create was exactly to get this network virtualization layer into the container config. Right, it's just that you provided that lxc.conf to lxc-create. lxc-create copied that to where it wanted that path to go - which is /var/lib/lxc/ubuntu1/config. lxc-create doesn't look at the template arguments. It's certainly gross that lxc-create passes information to the templates over the same channel that users do. Might be worth talking with upstream about changing that for next cycle. -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 875262] Re: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/sqlite.so'
I believe this was fixed by the latest precise merge with Debian. Can somebody please try out the upgrade to php5 5.3.10-1ubuntu1? Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/875262 Title: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626+lfs/sqlite.so' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/875262/+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 931229] Re: lxc containers do not retain configured ip on container reboot
This bug was fixed in the package lxc - 0.7.5-3ubuntu26 --- lxc (0.7.5-3ubuntu26) precise; urgency=low [ Ben Howard ] * 0043-tweak-templates.patch: - Add a macaddr to configs created by ubuntu-cloud template - Add ssh key injection, locales, and tarball specification support to ubuntu-cloud template. [ Serge Hallyn ] * (also in 0043-tweak-templates.patch) Add a macaddr to configs created by ubuntu template (LP: #931229) and allow an ssh key to be injected. * debian/control: add openssl as Recommends as it's now used by the templates. * 0044-lxc-destroy-rm-autos: remove autostart symlinks when deleting a container. (LP: #930525) -- Serge Hallyn serge.hal...@ubuntu.com Wed, 15 Feb 2012 23:33:12 -0600 ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- 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/931229 Title: lxc containers do not retain configured ip on container reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/931229/+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 930525] Re: lxc-destroy should remove symlink from /etc/lxc/auto/ if it exists
This bug was fixed in the package lxc - 0.7.5-3ubuntu26 --- lxc (0.7.5-3ubuntu26) precise; urgency=low [ Ben Howard ] * 0043-tweak-templates.patch: - Add a macaddr to configs created by ubuntu-cloud template - Add ssh key injection, locales, and tarball specification support to ubuntu-cloud template. [ Serge Hallyn ] * (also in 0043-tweak-templates.patch) Add a macaddr to configs created by ubuntu template (LP: #931229) and allow an ssh key to be injected. * debian/control: add openssl as Recommends as it's now used by the templates. * 0044-lxc-destroy-rm-autos: remove autostart symlinks when deleting a container. (LP: #930525) -- Serge Hallyn serge.hal...@ubuntu.com Wed, 15 Feb 2012 23:33:12 -0600 ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- 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/930525 Title: lxc-destroy should remove symlink from /etc/lxc/auto/ if it exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930525/+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 926550] Re: No way to test proposed updates to juju
** Changed in: juju Milestone: None = florence ** Changed in: juju Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/926550 Title: No way to test proposed updates to juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/926550/+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 933656] [NEW] euca-describe-instances --ipv4 does not include public ip address
Public bug reported: I am using euca2ools with Openstack Nova in Precise Pangolin. euca-describe-instances helpfully includes an --ipv4 option to display ip address information of my running instances. Unfortunately, it does not seem to include the instances public ip address when one is assigned to it. Example: $ euca-describe-instances --ipv4 i-13d5 RESERVATION r-k6z2uziw agy_project default INSTANCEi-13d5 ami-004c172.16.60.147172.16.60.147 running agy 1 m1.small2012-02-16T01:47:48Znova $ euca-allocate-address· ADDRESS 8.8.8.8 $ euca-associate-address -i i-13d5 8.8.8.8 ADDRESS 8.8.8.8i-13d5 What I see: $ euca-describe-instances --ipv4 i-13d5 RESERVATION r-k6z2uziw agy_project default INSTANCEi-13d5 ami-004c172.16.60.147172.16.60.147 running agy 1 m1.small2012-02-16T01:47:48Znova What I expect to see: $ euca-describe-instances --ipv4 i-13d5 RESERVATION r-k6z2uziw agy_project default INSTANCEi-13d5 ami-004c172.16.60.1478.8.8.8 running agy 1 m1.small2012-02-16T01:47:48Znova ** Affects: euca2ools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/933656 Title: euca-describe-instances --ipv4 does not include public ip address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/933656/+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 933656] Re: euca-describe-instances --ipv4 does not include public ip address
I forgot the software version. $ dpkg-query --show euca2ools euca2ools 2.0.0~bzr495-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/933656 Title: euca-describe-instances --ipv4 does not include public ip address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/933656/+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 932991] Re: nova-api reporting missing images after upgrade
** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/932991 Title: nova-api reporting missing images after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/932991/+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 578283] Re: [needs-packaging] asterisk-moh-opsound, asterisk-core-sounds
This should already be fixed. ** Changed in: asterisk (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/578283 Title: [needs-packaging] asterisk-moh-opsound, asterisk-core-sounds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/578283/+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 579045] Re: [needs-packaging] openr2 -- MFC/R2 call setup library
** Changed in: asterisk (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/579045 Title: [needs-packaging] openr2 -- MFC/R2 call setup library To manage notifications about this bug go to: https://bugs.launchpad.net/asterisk/+bug/579045/+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 930285] Re: lxc hpsa driver
(marking invalid in lxc as I don't believe lxc has anything to do with it) ** Changed in: lxc (Ubuntu) Status: New = Invalid -- 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/930285 Title: lxc hpsa driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930285/+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 925110] Re: lxc-ls fails as non-root sometimes (second bug)
*** This bug is a duplicate of bug 930430 *** https://bugs.launchpad.net/bugs/930430 ** This bug has been marked a duplicate of bug 930430 lxc-ls requires root access after deploying an LXC instance -- 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/925110 Title: lxc-ls fails as non-root sometimes (second bug) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925110/+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 811422] Re: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite
This bug was fixed in the package apache2 - 2.2.16-1ubuntu3.5 --- apache2 (2.2.16-1ubuntu3.5) maverick-security; urgency=low * SECURITY UPDATE: arbitrary code execution via crafted SetEnvIf directive (LP: #811422) - debian/patches/215_CVE-2011-3607.dpatch: validate length in server/util.c. - CVE-2011-3607 * SECURITY UPDATE: another mod_proxy reverse proxy exposure - debian/patches/216_CVE-2011-4317.dpatch: validate additional URIs in modules/mappers/mod_rewrite.c, modules/proxy/mod_proxy.c, server/protocol.c. - CVE-2011-4317 * SECURITY UPDATE: denial of service and possible code execution via type field modification within a scoreboard shared memory segment - debian/patches/218_CVE-2012-0031.dpatch: check type field in server/scoreboard.c. - CVE-2012-0031 * SECURITY UPDATE: cookie disclosure via Bad Request errors - debian/patches/219_CVE-2012-0053.dpatch: check lengths in server/protocol.c. - CVE-2012-0053 -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 14 Feb 2012 10:11:29 -0500 ** Changed in: apache2 (Ubuntu Lucid) Status: Confirmed = Fix Released -- 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/811422 Title: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/811422/+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 811422] Re: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite
This bug was fixed in the package apache2 - 2.2.14-5ubuntu8.8 --- apache2 (2.2.14-5ubuntu8.8) lucid-security; urgency=low * SECURITY UPDATE: arbitrary code execution via crafted SetEnvIf directive (LP: #811422) - debian/patches/215_CVE-2011-3607.dpatch: validate length in server/util.c. - CVE-2011-3607 * SECURITY UPDATE: another mod_proxy reverse proxy exposure - debian/patches/216_CVE-2011-4317.dpatch: validate additional URIs in modules/mappers/mod_rewrite.c, modules/proxy/mod_proxy.c, server/protocol.c. - CVE-2011-4317 * SECURITY UPDATE: denial of service and possible code execution via type field modification within a scoreboard shared memory segment - debian/patches/218_CVE-2012-0031.dpatch: check type field in server/scoreboard.c. - CVE-2012-0031 * SECURITY UPDATE: cookie disclosure via Bad Request errors - debian/patches/219_CVE-2012-0053.dpatch: check lengths in server/protocol.c. - CVE-2012-0053 -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 14 Feb 2012 10:36:43 -0500 ** Changed in: apache2 (Ubuntu Hardy) Status: Confirmed = Fix Released -- 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/811422 Title: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/811422/+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 811422] Re: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite
This bug was fixed in the package apache2 - 2.2.8-1ubuntu0.23 --- apache2 (2.2.8-1ubuntu0.23) hardy-security; urgency=low * SECURITY UPDATE: arbitrary code execution via crafted SetEnvIf directive (LP: #811422) - debian/patches/220_CVE-2011-3607.dpatch: validate length in server/util.c. - CVE-2011-3607 * SECURITY UPDATE: another mod_proxy reverse proxy exposure - debian/patches/221_CVE-2011-4317.dpatch: validate additional URIs in modules/mappers/mod_rewrite.c, modules/proxy/mod_proxy.c, server/protocol.c. - CVE-2011-4317 * SECURITY UPDATE: denial of service and possible code execution via type field modification within a scoreboard shared memory segment - debian/patches/222_CVE-2012-0031.dpatch: check type field in server/scoreboard.c. - CVE-2012-0031 * SECURITY UPDATE: cookie disclosure via Bad Request errors - debian/patches/223_CVE-2012-0053.dpatch: check lengths in server/protocol.c. - CVE-2012-0053 -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 14 Feb 2012 10:49:11 -0500 -- 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/811422 Title: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/811422/+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 811422] Re: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite
This bug was fixed in the package apache2 - 2.2.17-1ubuntu1.5 --- apache2 (2.2.17-1ubuntu1.5) natty-security; urgency=low * SECURITY UPDATE: arbitrary code execution via crafted SetEnvIf directive (LP: #811422) - debian/patches/215_CVE-2011-3607.dpatch: validate length in server/util.c. - CVE-2011-3607 * SECURITY UPDATE: another mod_proxy reverse proxy exposure - debian/patches/216_CVE-2011-4317.dpatch: validate additional URIs in modules/mappers/mod_rewrite.c, modules/proxy/mod_proxy.c, server/protocol.c. - CVE-2011-4317 * SECURITY UPDATE: denial of service via invalid cookie - debian/patches/217_CVE-2012-0021.dpatch: check name and value in modules/loggers/mod_log_config.c. - CVE-2012-0021 * SECURITY UPDATE: denial of service and possible code execution via type field modification within a scoreboard shared memory segment - debian/patches/218_CVE-2012-0031.dpatch: check type field in server/scoreboard.c. - CVE-2012-0031 * SECURITY UPDATE: cookie disclosure via Bad Request errors - debian/patches/219_CVE-2012-0053.dpatch: check lengths in server/protocol.c. - CVE-2012-0053 -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 14 Feb 2012 10:02:26 -0500 ** Changed in: apache2 (Ubuntu Maverick) Status: Confirmed = Fix Released -- 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/811422 Title: Exploitable integer overflow on x86 in mod SetEnvIf, leading to buffer overwrite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/811422/+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 933723] [NEW] resolvconf creating bogus resolv.conf file
You have been subscribed to a public bug: We're noticing this on every server we're installing Precise dailys on for sniff testing. First, we use DHCP exclusively in the certification labs for assigning IP info to machines. So while Stefan Bader ran into this with his static IP setup (https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/923685) we're seeing it with our dhcp set up. This is new behaviour also, I do not believe this was an issue in earlier Precise images, (alpha 2) so this seems to have been introduced since then. At some point, I assume during the install, the system /etc/resolv.conf is created using information gathered from the dhcp server and it gets a single entry that looks like this: nameserver 10.XXX.XXX.XXX However, as soon as resolvconf is installed, this all gets replaced by the resolvconf files, and our working resolv.conf becomes /etc/resolvconf/resolv.conf.d/original, which is ignored by resolvconf. After this, we get a useless resolvconf file that points to localhost: ubuntu@ubuntu:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search example.org Now, looking into /etc/resolvconf/resolv.conf.d, there are three files: base, head and original. ubuntu@ubuntu:/etc/resolvconf/resolv.conf.d$ cat base ubuntu@ubuntu:/etc/resolvconf/resolv.conf.d$ cat head # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN ubuntu@ubuntu:/etc/resolvconf/resolv.conf.d$ cat original nameserver 10.189.84.1 ubuntu@ubuntu:/etc/resolvconf/resolv.conf.d$ so right now, by default, resolvconf is breaking resolv.conf on dhcp setups (this is epidemic across our test labs) I CAN resolve (no pun intended) this by simply replacing /etc/resolv.conf with /etc/resolvconf/resolv.conf.d/original but that's only a very temporary bandaid and NOT desired as a resolution. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- resolvconf creating bogus resolv.conf file https://bugs.launchpad.net/bugs/933723 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 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
[Blueprint servercloud-p-freeipa-tech-preview] FreeIPA Tech Preview
Blueprint changed by Timo Aaltonen: Whiteboard changed: Rather fine-grained task list below. Uploading full 389ds stack is not necessary (hence status isn't BLOCKED), though not a whole lot of work after the prereqs are already done. Work items (precise-alpha-2): [tjaalton] package python-nss: DONE [tjaalton] upload python-nss: DONE [tjaalton] package python-krbv: DONE [tjaalton] upload python-krbv: DONE [tjaalton] package certmonger: DONE [tjaalton] upload certmonger: DONE [tjaalton] add gssapi delegation support for curl (merge from Debian): DONE [tjaalton] add gssapi delegation support for xmlrpc-c (patch from RHEL): DONE [tjaalton] package svrcore: DONE [tjaalton] upload svrcore: DONE [tjaalton] package libmozilla-ldap-perl: DONE [tjaalton] package 389-ds-base: DONE [tjaalton] test /usr/sbin/setup-ds: DONE [vorlon] Include ldif.h in libldap2-dev by updating openldap to =2.4.26: DONE [tjaalton] upload libmozilla-ldap-perl (needs new openldap): DONE [tjaalton] package ldapjdk: DONE [tjaalton] upload ldapjdk: DONE [tjaalton] package jss: DONE [tjaalton] upload jss: DONE [tjaalton] package idm-console-framework: DONE [tjaalton] package libapache2-mod-nss: DONE [tjaalton] package tomcatjss: DONE [tjaalton] package osutil: DONE [tjaalton] upload osutil: DONE [tjaalton] package dogtag-pki-theme: DONE - [tjaalton] package pki-core: DONE [tjaalton] package 389-adminutil: DONE [tjaalton] package 389-admin: DONE [tjaalton] package 389-admin-console: DONE [tjaalton] package 389-console: DONE [tjaalton] package 389-ds-console: DONE Work items (ubuntu-12.04-beta-1): - [tjaalton] upload 389-ds-base (needs new openldap, svrcore, libmozilla-ldap-perl): TODO + [tjaalton] package pki-core: INPROGRESS + [tjaalton] upload 389-ds-base: INPROGRESS [tjaalton] upload idm-console-framework (needs ldapjdk): INPROGRESS [tjaalton] upload libapache2-mod-nss: INPROGRESS [tjaalton] upload tomcatjss (needs jss): INPROGRESS [tjaalton] upload dogtag-pki-theme: TODO [tjaalton] upload pki-core (needs ldapjdk, jss, osutil, tomcatjss): TODO [tjaalton] package slapi-nis, or drop NIS support from freeipa (if possible): TODO [tjaalton] upload slapi-nis: TODO - [tjaalton] package freeipa: INPROGRESS - [tjaalton] upload freeipa: BLOCKED + [tjaalton] package freeipa-client: DONE + [tjaalton] upload freeipa-client: INPROGRESS + [tjaalton] package pki-core: INPROGRESS + [tjaalton] package freeipa-server: INPROGRESS + [tjaalton] upload freeipa-server: BLOCKED [tjaalton] test /usr/sbin/ipa-client-install: INPROGRESS [tjaalton] test /usr/sbin/ipa-server-install: TODO Work items: - [tjaalton] package 389-dsgw: INPROGRESS + [tjaalton] package 389-dsgw: DONE [tjaalton] package 389-ds meta package: INPROGRESS [tjaalton] upload 389-adminutil: INPROGRESS - upload 389-admin (needs 389-adminutil, 389-ds-base, libapache2-mod-nss, libmozilla-ldap-perl): TODO - upload 389-admin-console (needs jss, ldapjdk, idm-console-framework): TODO + [tjaalton] upload 389-admin (needs 389-adminutil, 389-ds-base, libapache2-mod-nss): INPROGRESS + [tjaalton] upload 389-dsgw: INPROGRESS + [tjaalton] upload 389-admin-console (needs idm-console-framework): INPROGRESS upload 389-console: TODO upload 389-ds-console: TODO - upload 389-dsgw: TODO upload 389-ds: TODO + + tjaalton -- 2012-02-16: FF today, so pushing everything that's verified + to be finished. Splitting freeipa-client apart from the server, that can + be worked on separately. Client got uploaded to precise. -- FreeIPA Tech Preview https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-freeipa-tech-preview -- 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 933723] Re: resolvconf creating bogus resolv.conf file
** Changed in: bind9 (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/933723 Title: resolvconf creating bogus resolv.conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+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 933723] Re: resolvconf creating bogus resolv.conf file
The resolvconf /usr/share/doc/resolvconf/README.gz also points to a Debian bug report for bind9: http://bugs.debian.org/483098 It seems that, *either* bind9 should not inject itself into resolvconf by default, *or* bind9 should completely integrate with resolvconf and pick up upstream resolver info from other sources. ** Also affects: bind9 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098 Importance: Unknown Status: Unknown ** Changed in: bind9 (Ubuntu) Assignee: (unassigned) = LaMont Jones (lamont) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/933723 Title: resolvconf creating bogus resolv.conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+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 933723] Re: resolvconf creating bogus resolv.conf file
Spoke with Jeff on IRC; apparently he's getting bind9 installed when he wasn't expecting it, and this is where resolv.conf is being pointed. So the bug here is with bind9: the debconf question bind9/run-resolvconf defaults to 'true', which means that if resolvconf is present (which, as of 12.04, it always is), it automatically registers itself as a caching nameserver - but at least in some cases is failing to actually resolve anything. This may be particular to the case where you have a firewall blocking access to port 53 on the public Internet and are required to use the DHCP-provided DNS information. In that case, installing bind9 is probably a bad idea... but just to be sure, assigning this bug to bind9 so we can consider whether bind9 should be hooking into resolvconf by default. ** Package changed: resolvconf (Ubuntu) = bind9 (Ubuntu) ** Changed in: bind9 (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/933723 Title: resolvconf creating bogus resolv.conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+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 933480] Re: Picks hmac-md5 over hmac-sha1
For precise, openssh-5.9 supports even more secure algorithms, so the line should perhaps be: MACs hmac-sha2-512,hmac-sha2-256,hmac-sha1,hmac-ripemd160,umac...@openssh.com,hmac-md5,hmac-sha1-96,hmac-sha2-512-96,hmac-sha2-256-96,hmac-md5-96 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/933480 Title: Picks hmac-md5 over hmac-sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/933480/+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 933723] Re: resolvconf creating bogus resolv.conf file
At the very least, this behavior is awkward because it means installing bind9 on a machine will immediately break nameservice until it's configured, even if the admin *knows* that this configuration is needed and is planning to address it ASAP. So I think bind9 should probably not inject itself into resolvconf by default. I also think the cert lab should probably fix its install tests to not pull in an unconfigured bind9 server while testing. ** Bug watch added: Debian Bug tracker #483098 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/933723 Title: resolvconf creating bogus resolv.conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+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 933779] [NEW] lxc-start-ephemeral intermittently fails to connect to container
Public bug reported: We believe sshd just hasn't started quickly enough, sometimes. Graham Binns worked out this kind of solution, if it works for you: http://pastebin.ubuntu.com/844925/ (see lines 146-157 in particular). Thanks Gary ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/933779 Title: lxc-start-ephemeral intermittently fails to connect to container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/933779/+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 869635] Re: long delay at shutdown/reboot - network-manager doesn't close correctly
** Also affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/869635 Title: long delay at shutdown/reboot - network-manager doesn't close correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/869635/+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 869635] Re: long delay at shutdown/reboot - network-manager doesn't close correctly
** Package changed: dhcp3 (Ubuntu) = isc-dhcp (Ubuntu) ** Changed in: isc-dhcp (Ubuntu) Status: New = In Progress ** Changed in: isc-dhcp (Ubuntu) Importance: Undecided = High ** Changed in: isc-dhcp (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/869635 Title: long delay at shutdown/reboot - network-manager doesn't close correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/869635/+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 933779] Re: lxc-start-ephemeral intermittently fails to connect to container
** Changed in: lxc (Ubuntu) Status: New = Confirmed ** Changed in: lxc (Ubuntu) Importance: Undecided = High -- 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/933779 Title: lxc-start-ephemeral intermittently fails to connect to container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/933779/+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 933827] [NEW] smbd does not log anything to /var/log
Public bug reported: I run smbd, but nothing happens. I also try service smbd start, but nothing happens. When I look in /var/log/ there is no samba log or folder, so I don't know what is wrong. I haven't changed anything in smbd.conf. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/933827 Title: smbd does not log anything to /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/933827/+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 898373] Re: fsck.ext3: Device or resource busy while trying to open /dev/xvda2
This bug was fixed in the package cloud-init - 0.6.3~bzr519-0ubuntu1 --- cloud-init (0.6.3~bzr519-0ubuntu1) precise; urgency=low * New upstream snapshot. - [Mike Milner] add support for managing CA Certificates (LP: #915232) - in ci-info lines, use '.' to for empty field for easier machine reading - support empty lines in #include files (LP: #923043) - [Jef Baeur] support configuration of salt minions Bauer) (LP: #927795) - DataSourceOVF: only search for OVF data on ISO9660 filesystems (LP: #898373) - DataSourceConfigDrive: support getting data from openstack config drive (LP: #857378) - [Juerg Haefliger] formating and pylint cleanups * increase timeouts for initial config check for metadata service to address slow metadata service in openstack * add awareness of ConfigDrive data source -- Scott Moser smo...@ubuntu.com Thu, 16 Feb 2012 17:27:05 -0500 ** Branch linked: lp:ubuntu/cloud-init ** Changed in: cloud-init (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/898373 Title: fsck.ext3: Device or resource busy while trying to open /dev/xvda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/898373/+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 857378] Re: make a DataSource supporting simple local media (configdrive, simple iso)
This bug was fixed in the package cloud-init - 0.6.3~bzr519-0ubuntu1 --- cloud-init (0.6.3~bzr519-0ubuntu1) precise; urgency=low * New upstream snapshot. - [Mike Milner] add support for managing CA Certificates (LP: #915232) - in ci-info lines, use '.' to for empty field for easier machine reading - support empty lines in #include files (LP: #923043) - [Jef Baeur] support configuration of salt minions Bauer) (LP: #927795) - DataSourceOVF: only search for OVF data on ISO9660 filesystems (LP: #898373) - DataSourceConfigDrive: support getting data from openstack config drive (LP: #857378) - [Juerg Haefliger] formating and pylint cleanups * increase timeouts for initial config check for metadata service to address slow metadata service in openstack * add awareness of ConfigDrive data source -- Scott Moser smo...@ubuntu.com Thu, 16 Feb 2012 17:27:05 -0500 ** Branch linked: lp:ubuntu/cloud-init ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/857378 Title: make a DataSource supporting simple local media (configdrive, simple iso) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/857378/+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 933779] Re: lxc-start-ephemeral intermittently fails to connect to container
This bug was fixed in the package lxc - 0.7.5-3ubuntu27 --- lxc (0.7.5-3ubuntu27) precise; urgency=low [ Graham Binns ] * debian/local/lxc-start-ephemeral: retry ssh in case sshd was slow in starting. (LP: #933779) -- Serge Hallyn serge.hal...@ubuntu.com Thu, 16 Feb 2012 16:47:03 -0600 ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- 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/933779 Title: lxc-start-ephemeral intermittently fails to connect to container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/933779/+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
Re: [Bug 925513] Re: plymouth should not run in container
On Thu, Feb 16, 2012 at 02:25:36PM -, Serge Hallyn wrote: regarding whether disabling plymouth is the right fix: I don't know the mechanisms plymouth uses. Well, I'm happy to answer questions you have on this, but I don't understand what issue you're trying to address by disabling plymouth. The bug description says only that: As stgraber said, it writes some error messages to /var/log/upstart (when you have logging) and sometimes to the console. But a) that's not true for values of it == plymouth (maybe this refers to upstart?), and b) it's not clear to me what behavior you expect for the various messages if plymouth is disabled - particularly the ones that are *actually* being routed to plymouth, which may require some sort of user interaction. 1. for system log entries, the right fix will be a syslog namespace, which doesn't yet exist. plymouth has nothing to do with syslog. It captures *console* output to /var/log/boot.log, but that's a secondary function and doesn't use syslog for output. 2. if it uses proc files, we may be able to use apparmor to protect from plymouth, though that may make plymouth fail and cause the container to not boot right. The right fix would be a mix of user namespaces and proc file access filtering. Plymouth uses /proc/cmdline and /proc/self/fd. Are these a problem in lxc? 3. if it uses devices (ioctls or writes), we may be able to use apparmor and/or the devices namespace to protect from plymouth, but a device namespace will be the right fix. Oh, it definitely uses devices. At a minimum, it expects to be able to open /dev/console. It also generally expects to make use of /dev/fb, /dev/tty0, /dev/tty1, and a few others. I had assumed that there is some sort of virtualized console in the container that would be exposed with the usual device name. If there isn't, then there's definitely no point in running plymouth in a container. -- 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/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 933818] Re: public-ipv4 metadata url not working
Looking at it a bit more with Daviey, it turns out the later calls thru the network layer will update the cache, but we never get that far because its consistently returning an outdated cache hit with an empty floating_ips list. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/933818 Title: public-ipv4 metadata url not working To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/933818/+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 927803] Re: Fails to launch recovery menu when (at least) Postfix installed
I think this is a bug in both postfix and friendly-recovery. - resolvconf will always be run in early boot, to ensure that /etc/resolv.conf is available ASAP - *before* the root filesystem is mounted read-write. Any resolvconf hooks, such as /etc/resolvconf /update-libc.d/postfix, *must* account for this and not exit non-zero if the filesystem is not yet writable. (The hook can and should be a no-op at this point in the boot, because the postfix init script which runs later will do its own copy of /etc/resolv.conf into the chroot.) - friendly-recovery should not care about the exit status of the initctl emit command. It should still wait for all dependent events to trigger in order to not race, but it should not care if one of the dependent jobs has failed. So this is a medium-severity bug in friendly-recovery, and a high- severity bug in postfix. ** Also affects: postfix (Ubuntu) Importance: Undecided Status: New ** Changed in: friendly-recovery (Ubuntu) Importance: Undecided = Medium ** Changed in: friendly-recovery (Ubuntu) Status: New = Triaged ** Changed in: postfix (Ubuntu) Status: New = Triaged ** Changed in: postfix (Ubuntu) Importance: Undecided = High -- 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/927803 Title: Fails to launch recovery menu when (at least) Postfix installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/927803/+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 924002] Re: build system strips binaries, so no debug symbol packages available
Confirmed that just asking the build system to not strip the binaries results in the symbols being stripped into appropriate dbgsym packages. I've uploaded that change. @Adam: Your debdiff would make a useful addition to the Debian packages, if they care about having debugging symbols. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/924002 Title: build system strips binaries, so no debug symbol packages available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/924002/+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 924002] Re: build system strips binaries, so no debug symbol packages available
This bug was fixed in the package autofs5 - 5.0.6-0ubuntu3 --- autofs5 (5.0.6-0ubuntu3) precise; urgency=low * debian/rules: - Don't strip symbols during the build; let dh_strip turn them into dbgsym packages instead. Thanks, Adam Stokes! (LP: #924002) -- Christopher James Halse Rogers christopher.halse.rog...@canonical.com Fri, 17 Feb 2012 11:59:50 +1100 ** Changed in: autofs5 (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/924002 Title: build system strips binaries, so no debug symbol packages available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/924002/+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 927803] Re: Fails to launch recovery menu when (at least) Postfix installed
Thomas, is there any chance that you have postfix installed in the environment where you're seeing the resolvconf job fail at boot? If so, this postfix resolvconf hook script probably explains what you're seeing. (And if you don't have postfix installed, it could be a different hook script causing a similar 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/927803 Title: Fails to launch recovery menu when (at least) Postfix installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/927803/+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 697181] Re: DoS: Infinite loop processing 2.2250738585072011e-308
** Branch linked: lp:ubuntu/hardy-updates/php5 ** Branch linked: lp:ubuntu/php5 ** Branch linked: lp:ubuntu/dapper-updates/php5 ** Branch linked: lp:ubuntu/maverick-security/php5 ** Branch linked: lp:ubuntu/karmic-security/php5 ** Branch linked: lp:ubuntu/lucid-security/php5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/697181 Title: DoS: Infinite loop processing 2.2250738585072011e-308 To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/697181/+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 592442] Re: fopen fails on some SSL urls
** Branch linked: lp:ubuntu/php5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/592442 Title: fopen fails on some SSL urls To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/592442/+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 910296] Re: Please backport the upstream patch to prevent attacks based on hash collisions
** Branch linked: lp:ubuntu/natty-security/php5 ** Branch linked: lp:ubuntu/maverick-security/php5 ** Branch linked: lp:ubuntu/lucid-security/php5 ** Branch linked: lp:ubuntu/oneiric-updates/php5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/910296 Title: Please backport the upstream patch to prevent attacks based on hash collisions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/910296/+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
Re: [Bug 925513] Re: plymouth should not run in container
Quoting Steve Langasek (steve.langa...@canonical.com):
On Thu, Feb 16, 2012 at 02:25:36PM -, Serge Hallyn wrote:
regarding whether disabling plymouth is the right fix: I don't know the
mechanisms plymouth uses.
Well, I'm happy to answer questions you have on this, but I don't understand
what issue you're trying to address by disabling plymouth. The bug
description says only that:
As stgraber said, it writes some error messages to /var/log/upstart (when
you have logging) and sometimes to the console.
But a) that's not true for values of it == plymouth (maybe this refers
to upstart?), and b) it's not clear to me what behavior you expect for the
various messages if plymouth is disabled - particularly the ones that are
*actually* being routed to plymouth, which may require some sort of user
interaction.
1. for system log entries, the right fix will be a syslog namespace,
which doesn't yet exist.
plymouth has nothing to do with syslog. It captures *console* output to
/var/log/boot.log, but that's a secondary function and doesn't use syslog
for output.
Does it write it straight to /var/log/boot.log, or does it do it through
syslog(2) or syslog(3)? If it writes straight to /var/log/boot.log then
there should be no problem.
2. if it uses proc files, we may be able to use apparmor to protect from
plymouth, though that may make plymouth fail and cause the container to
not boot right. The right fix would be a mix of user namespaces and
proc file access filtering.
Plymouth uses /proc/cmdline and /proc/self/fd. Are these a problem in
lxc?
/proc/self/fd is correct. /proc/cmdline will be the host's kernel
cmdline, which shouldn't exactly be a problem but may be misleading.
3. if it uses devices (ioctls or writes), we may be able to use apparmor
and/or the devices namespace to protect from plymouth, but a device
namespace will be the right fix.
Oh, it definitely uses devices. At a minimum, it expects to be able to open
/dev/console. It also generally expects to make use of /dev/fb, /dev/tty0,
/dev/tty1, and a few others. I had assumed that there is some sort of
virtualized console in the container that would be exposed with the usual
device name. If there isn't, then there's definitely no point in running
plymouth in a container.
/dev/console and /dev/tty{1-4} are bind-mounted pty devices, and are ok
for it to use. /dev/fb is not available in the container - I don't see
/dev/fb0 at all, and the devices cgroup will refuse the container the
rights to read or write it. Otherwise it would be a problem as that is
not virtualized.
Steve, it sounds to me like we should mark this bug as wontfix.
--
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/925513
Title:
plymouth should not run in container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 925513] Re: plymouth should not run in container
Does it write it straight to /var/log/boot.log, or does it do it through
syslog(2) or syslog(3)? If it writes straight to /var/log/boot.log then
there should be no problem.
Yes, it's straight to the log file.
/dev/console and /dev/tty{1-4} are bind-mounted pty devices, and are ok
for it to use. /dev/fb is not available in the container - I don't see
/dev/fb0 at all, and the devices cgroup will refuse the container the
rights to read or write it. Otherwise it would be a problem as that is
not virtualized.
Well, if /dev/fb0 isn't available, plymouth should automatically fall
back to using the console in text-only mode.
Steve, it sounds to me like we should mark this bug as wontfix.
Ok, done.
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Won't Fix
--
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/925513
Title:
plymouth should not run in container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+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 927803] Re: Fails to launch recovery menu when (at least) Postfix installed
** Branch linked: lp:ubuntu/postfix -- 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/927803 Title: Fails to launch recovery menu when (at least) Postfix installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/927803/+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 927803] Re: Fails to launch recovery menu when (at least) Postfix installed
This bug was fixed in the package postfix - 2.8.7-1ubuntu1 --- postfix (2.8.7-1ubuntu1) precise; urgency=low * debian/update-libc.d: before we try to copy the resolv.conf over, just check if the service is running by calling /etc/init.d/postfix status. If it's not running, there's never a need to copy, and if it's running we know the package is installed - making other checks superfluous and ensuring our hook doesn't exit non-zero if called before /var is mounted read-write. LP: #927803. -- Steve Langasek steve.langa...@ubuntu.com Thu, 16 Feb 2012 17:53:51 -0800 ** Changed in: postfix (Ubuntu) Status: Triaged = Fix Released -- 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/927803 Title: Fails to launch recovery menu when (at least) Postfix installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/927803/+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 933818] Re: public-ipv4 metadata url not working
Work being done in the proposal would help here, too: https://review.openstack.org/#change,4269 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/933818 Title: public-ipv4 metadata url not working To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/933818/+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 934011] [NEW] package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 10.04 Package: postfix 2.7.0-1ubuntu0.2 ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21 Uname: Linux 2.6.32-38-generic i686 Architecture: i386 Date: Fri Feb 17 12:55:04 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 75 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) SourcePackage: postfix Title: package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- 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/934011 Title: package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/934011/+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 934011] Re: package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
-- 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/934011 Title: package postfix 2.7.0-1ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/934011/+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 933304] [NEW] Ubuntu Precise 12.04 remote desktop options not in system settings where you would expect
Public bug reported: Ubuntu 12.04 does not have any remote desktop options in the system settings section where I would expect them to be. They currently have to be configured ueing a separate Desktop Sharing application. This should be integrated into the System Settings section, probably under what was the screen section, which has now been renamed to brightness and lock (which is not particularly a good name as birghtness is only there on laptops and so may confuse people). ** Affects: vino (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933304 Title: Ubuntu Precise 12.04 remote desktop options not in system settings where you would expect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/933304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933303] [NEW] Please upgrade aweather to version 0.7
Public bug reported: Please update aweather to version 0.7 The upstream release of AWeather 0.7 occurred very recently and I would like for it to be included in Ubuntu Precise. I'm not sure if there will be time before the Feature Freeze to get this pushed through Debian so I've packaged it in the AWeather PPA for Ubuntu Precise: https://launchpad.net/~andy753421/+archive/aweather The version in the PPA contains one patch by Daniel T Chen that removes a call to g_thread_init(), which is now deprecated. This package depends on version 0.7 of libgrits: https://bugs.launchpad.net/ubuntu/+source/libgrits/+bug/933299 Could someone please check this and upload it for Ubuntu Precise? Thank you ** Affects: aweather (Ubuntu) Importance: Undecided Status: New ** Description changed: Please update aweather to version 0.7 - The upstream release of AWeather 0.7 occurred very recently and I would like for - it to be included in Ubuntu Precise. I'm not sure if there will be time before - the Feature Freeze to get this pushed through Debian so I've packaged it in the - AWeather PPA for Ubuntu Precise: + The upstream release of AWeather 0.7 occurred very recently and I would + like for it to be included in Ubuntu Precise. I'm not sure if there will + be time before the Feature Freeze to get this pushed through Debian so + I've packaged it in the AWeather PPA for Ubuntu Precise: https://launchpad.net/~andy753421/+archive/aweather - The version in the PPA contains one patch by Daniel T Chen that removes a call - to g_thread_init(), which is now deprecated. + The version in the PPA contains one patch by Daniel T Chen that removes + a call to g_thread_init(), which is now deprecated. This package depends on version 0.7 of libgrits: https://bugs.launchpad.net/ubuntu/+source/libgrits/+bug/933299 Could someone please check this and upload it for Ubuntu Precise? Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933303 Title: Please upgrade aweather to version 0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aweather/+bug/933303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933299] Re: Please upgrade libgrits to version 0.7
** Description changed: Please update libgrits to version 0.7 - The upstream release of version Grits 0.7 occurred very recently and I would - like for it to be included in Ubuntu Precise. I'm not sure if there will be time - before the Feature Freeze to get this pushed through Debian so I've packaged it - in the AWeather PPA for Ubuntu Precise: + The upstream release of Grits 0.7 occurred very recently and I would + like for it to be included in Ubuntu Precise. I'm not sure if there will + be time before the Feature Freeze to get this pushed through Debian so + I've packaged it in the AWeather PPA for Ubuntu Precise: https://launchpad.net/~andy753421/+archive/aweather - The version in the PPA contains one patch that adds an explicit dependency on - gmodule-2.0 to the configure.ac script, which is needed to build correctly on - Ubuntu Precise. + The version in the PPA contains one patch that adds an explicit + dependency on gmodule-2.0 to the configure.ac script, which is needed to + build correctly on Ubuntu Precise. Could someone please check this and upload it for Ubuntu Precise? Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933299 Title: Please upgrade libgrits to version 0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgrits/+bug/933299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922656] Re: Analog-output-lfe-on-mono is only output option
Please re-read comment #12, for instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922656 Title: Analog-output-lfe-on-mono is only output option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/922656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918769] Re: X blink with Vostro 360 and Ubuntu Oneiric and Precise
Hi, Is there any thing i can do to help solving this problem ? Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918769 Title: X blink with Vostro 360 and Ubuntu Oneiric and Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/918769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901636] Re: update-apt-xapian-index takes way too much cpu cycles
*** This bug is a duplicate of bug 363695 *** https://bugs.launchpad.net/bugs/363695 ** This bug has been marked a duplicate of bug 363695 update-apt-xapian-index uses too much CPU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901636 Title: update-apt-xapian-index takes way too much cpu cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/901636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881262] Re: LibreOffice cannot open files on the network (gvfs)
*** This bug is a duplicate of bug 793622 *** https://bugs.launchpad.net/bugs/793622 I disagrree on the duplication status. I do not have wicd installed on my system. Besides bug #793622 is talking about aesthetics en config file locations. Bug #881262 is something that does not work. Please clarify or fix status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881262 Title: LibreOffice cannot open files on the network (gvfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/881262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933305] [NEW] window buttons have dark text on dark bg
Public bug reported: In Precise Daily (i386) 20120216, window buttons in GNOME Fallback Mode have dark text on dark bg, making it really hard to read. ** Affects: light-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933305 Title: window buttons have dark text on dark bg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/933305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933305] Re: window buttons have dark text on dark bg
** Attachment added: Screenshot showing the mis-behavior https://bugs.launchpad.net/bugs/933305/+attachment/2744553/+files/ubuntu12.04-classic-session.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933305 Title: window buttons have dark text on dark bg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/933305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886159] Re: desktopcouch Value error cannot covert float Nan to integer
FYI - I've filed http://bugs.python.org/issue14028 to track this as well from the Python side. ** Bug watch added: Python Roundup #14028 http://bugs.python.org/issue14028 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886159 Title: desktopcouch Value error cannot covert float Nan to integer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/886159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926473] Re: upstart test suite assumes no inherited fds
This bug was fixed in the package upstart - 1.4-0ubuntu7 --- upstart (1.4-0ubuntu7) precise; urgency=low * debian/manpages/upstart-events.7: Added missing events 'container' and 'not-container'. * Update 'runlevel' event emission time in upstart-events(7) (LP: #921501). * Merge of important upstream log fixes to avoid spinning when a job which leaks fds (such as 'sshd -D') is stopped (LP: #926468). * Merge of lp:~jamesodhunt/upstart/early-job-log-flush to allow jobs that _end_ very early in the boot to have their output logged. * debian/conf/flush-early-job-log.conf: Upstart job to force flushing of early job log output data when disk becomes writeable. * Re-enable job logging by default. [ Steve Langasek ] * init/tests/test_job_process.c: close all fds before running tests that check for unexpected open fds, so that files leaked from the environment don't cause the test suite to fail gratuitously. LP: #926473. * bump debhelper compat to 9 and adjust debian/rules to use the dpkg-buildflags interfaces, so that upstart can be cross-compiled and also so we pick up any future hardening flags for free. -- Steve Langasek steve.langa...@ubuntu.com Thu, 16 Feb 2012 07:52:11 + ** Changed in: upstart (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926473 Title: upstart test suite assumes no inherited fds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/926473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926468] Re: Stopping ssh with a logged in user causes init to spin at 100%
This bug was fixed in the package upstart - 1.4-0ubuntu7 --- upstart (1.4-0ubuntu7) precise; urgency=low * debian/manpages/upstart-events.7: Added missing events 'container' and 'not-container'. * Update 'runlevel' event emission time in upstart-events(7) (LP: #921501). * Merge of important upstream log fixes to avoid spinning when a job which leaks fds (such as 'sshd -D') is stopped (LP: #926468). * Merge of lp:~jamesodhunt/upstart/early-job-log-flush to allow jobs that _end_ very early in the boot to have their output logged. * debian/conf/flush-early-job-log.conf: Upstart job to force flushing of early job log output data when disk becomes writeable. * Re-enable job logging by default. [ Steve Langasek ] * init/tests/test_job_process.c: close all fds before running tests that check for unexpected open fds, so that files leaked from the environment don't cause the test suite to fail gratuitously. LP: #926473. * bump debhelper compat to 9 and adjust debian/rules to use the dpkg-buildflags interfaces, so that upstart can be cross-compiled and also so we pick up any future hardening flags for free. -- Steve Langasek steve.langa...@ubuntu.com Thu, 16 Feb 2012 07:52:11 + ** Changed in: upstart (Ubuntu Precise) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926468 Title: Stopping ssh with a logged in user causes init to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/926468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921501] Re: runlevel time incorrect in Table 1 of upstart-events(7)
This bug was fixed in the package upstart - 1.4-0ubuntu7 --- upstart (1.4-0ubuntu7) precise; urgency=low * debian/manpages/upstart-events.7: Added missing events 'container' and 'not-container'. * Update 'runlevel' event emission time in upstart-events(7) (LP: #921501). * Merge of important upstream log fixes to avoid spinning when a job which leaks fds (such as 'sshd -D') is stopped (LP: #926468). * Merge of lp:~jamesodhunt/upstart/early-job-log-flush to allow jobs that _end_ very early in the boot to have their output logged. * debian/conf/flush-early-job-log.conf: Upstart job to force flushing of early job log output data when disk becomes writeable. * Re-enable job logging by default. [ Steve Langasek ] * init/tests/test_job_process.c: close all fds before running tests that check for unexpected open fds, so that files leaked from the environment don't cause the test suite to fail gratuitously. LP: #926473. * bump debhelper compat to 9 and adjust debian/rules to use the dpkg-buildflags interfaces, so that upstart can be cross-compiled and also so we pick up any future hardening flags for free. -- Steve Langasek steve.langa...@ubuntu.com Thu, 16 Feb 2012 07:52:11 + ** Changed in: upstart (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921501 Title: runlevel time incorrect in Table 1 of upstart-events(7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/921501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933308] [NEW] cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration
Public bug reported: With upstart logging enabled, the cups upstart job routinely spits the following error out to /var/log/upstart/cups.log: cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration Indeed, cups seems to get around to creating the socket several seconds after the cups post-start script stops waiting for it. $ ls -l --full-time /var/log/upstart/cups.log -rw-r- 1 root root 90 2012-02-15 22:23:01.937144478 -0800 /var/log/upstart/cups.log $ ls -l --full-time /var/run/cups/cups.sock srwxrwxrwx 1 root root 0 2012-02-15 22:23:13.261144768 -0800 /var/run/cups/cups.sock $ So it doesn't look like a 3 second timeout is realistically long enough here. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.2-3 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9 CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e Date: Thu Feb 16 00:03:35 2012 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) Lpstat: device for davidson-printer: smb://WORKGROUP/EXCALIBUR/Printer2 device for HP-Color-LaserJet-CM1312-MFP: hp:/usb/HP_Color_LaserJet_CM1312_MFP?serial=00CNB882VG58 device for HP-PSC-750: ipp://207.224.24.210:631/printers/PSC_750 device for HP-PSC-750-legal: ipp://207.224.24.210:631/printers/PSC_750 MachineType: LENOVO 3249CTO Papersize: letter PpdFiles: HP-PSC-750: HP PSC 750, hpcups 3.12.2 davidson-printer: HP Color LaserJet CP3505 Postscript (recommended) HP-Color-LaserJet-CM1312-MFP: HP Color LaserJet CM1312 MFP Series Postscript (recommended) HP-PSC-750-legal: HP PSC 750, hpcups 3.12.2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-16-generic root=/dev/mapper/hostname-root ro pcie_aspm=force i915.i915_enable_rc6=1 quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2011-11-08 (99 days ago) dmi.bios.date: 08/23/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET52WW (1.22 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [modified] modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.cups.cupsd.conf: 2011-08-09T08:12:10.630009 mtime.conffile..etc.default.cups: 2010-09-25T01:44:40.784776 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933308 Title: cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/933308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933308] Re: cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933308 Title: cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/933308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932807] Re: applications grab custom navigation shortcuts
** Package changed: unity (Ubuntu) = compiz (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932807 Title: applications grab custom navigation shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/932807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929888] Re: ldap_result returns -1 when called from sssd
Upstream bug at http://www.openldap.org/its/index.cgi?findid=7167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929888 Title: ldap_result returns -1 when called from sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929888] Re: ldap_result returns -1 when called from sssd
Ryan, can you build openldap with the proposed patch and test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929888 Title: ldap_result returns -1 when called from sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927369] Re: Update ruby-sass to last version (3.1.14)
Builds fine, syncing ** Changed in: ruby-sass (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: ruby-sass (Ubuntu) Assignee: Paolo Rotolo (paolorotolo) = Micah Gersten (micahg) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927369 Title: Update ruby-sass to last version (3.1.14) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-sass/+bug/927369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929464] Re: Error en la sincronización de archivos. (org.freedesktop.DBus.Error.NoReply: )
*** This bug is a duplicate of bug 927572 *** https://bugs.launchpad.net/bugs/927572 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntuone-client (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929464 Title: Error en la sincronización de archivos. (org.freedesktop.DBus.Error.NoReply: ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/929464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930936] Re: Xorg crashes after connect bluetooth keyboard
The attachment midispcur.c.patch of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report. [This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930936 Title: Xorg crashes after connect bluetooth keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/930936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 927908] Re: rpc.idmapd refuses to start
On Thu, 16 Feb 2012 00:35:27 -, Steve Langasek
steve.langa...@canonical.com wrote:
Oh, of course; the stop/pre-start message is precisely because the '|| {
stop; exit 0; }' is being called, and this is the output of the stop
command. So somehow, the job is failing to properly handle the
NEED_IDMAPD setting in /etc/default/nfs-common. Could you attach this
file as well?
Thanks for the hint!!
just mentioned that i set NEED_IDMAPD=y instead of =yes
Now the idmapd job can be started with service idmapd start.
However the logfile is empty:
local@vogone:~$ cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid
alternatives
# for the NEED_ options are yes and no.
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=
# Options for rpc.statd.
# Should rpc.statd listen on a specific port? This is especially useful
# when you have a port-based firewall. To use a fixed port, set this
# this variable to a statd argument like: --port 4000 --outgoing-port
4001.
# For more information, see rpc.statd(8) or
http://wiki.debian.org/SecuringNFS
STATDOPTS=
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=yes
# Do you want to start the gssd daemon? It is required for Kerberos
mounts.
NEED_GSSD=
local@vogone:~$ sudo vim /etc/default/nfs-common
[sudo] password for local:
local@vogone:~$ sudo service idmapd restart
restart: Unknown instance:
local@vogone:~$ sudo service idmapd start
idmapd start/running, process 2295
local@vogone:~$ cat /var/log/idmapd.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927908
Title:
rpc.idmapd refuses to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/927908/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933311] [NEW] asus 1015-pem keyboard can not deactivate numlock
Public bug reported: Dear Developers, I use Ubuntu 12.04 with latest updates, and have got a ASUS 1015 PEM netbook. When I login by Unity or Gnome Shell, I can not use my right hand keys because it comes Numlock by default, and i can not deactivate it. Now I write this from wmii environment and it does not occur. Thanks for your help ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 1.91-0ubuntu1 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,vpswitch,move,place,imgpng,resize,grid,mousepoll,snap,session,regex,gnomecompat,animation,wall,fade,workarounds,expo,winrules,scale,ezoom,unityshell] Date: Thu Feb 16 10:12:13 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120128) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933311 Title: asus 1015-pem keyboard can not deactivate numlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/933311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933311] Re: asus 1015-pem keyboard can not deactivate numlock
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933311 Title: asus 1015-pem keyboard can not deactivate numlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/933311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933310] [NEW] package virtualbox-ose-dkms (not installed) failed to install/upgrade: virtualbox-ose kernel module failed to build
Public bug reported: Get errors when trying to install virtualbox using the Ubuntu Software Center ProblemType: Package DistroRelease: Ubuntu 10.04 Package: virtualbox-ose-dkms (not installed) ProcVersionSignature: Ubuntu 2.6.38-11.50~lucid1-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Wed Feb 15 12:13:34 2012 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-hwe-lowell-i386-20111208-0 ErrorMessage: virtualbox-ose kernel module failed to build InstallationMedia: Ubuntu 10.04 Lucid - Build i386 LIVE/INSTALL Binary 20111208-04:32 PackageVersion: 3.1.6-dfsg-2ubuntu2 SourcePackage: virtualbox-ose Title: package virtualbox-ose-dkms (not installed) failed to install/upgrade: virtualbox-ose kernel module failed to build ** Affects: virtualbox-ose (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933310 Title: package virtualbox-ose-dkms (not installed) failed to install/upgrade: virtualbox-ose kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/933310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933310] Re: package virtualbox-ose-dkms (not installed) failed to install/upgrade: virtualbox-ose kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933310 Title: package virtualbox-ose-dkms (not installed) failed to install/upgrade: virtualbox-ose kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/933310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932807] Re: applications grab custom navigation shortcuts
*** This bug is a duplicate of bug 931927 *** https://bugs.launchpad.net/bugs/931927 This sounds like bug 931927. ** This bug has been marked a duplicate of bug 931927 [regression] Customized shortcuts don't work in compiz 1:0.9.7.0~bzr2995-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932807 Title: applications grab custom navigation shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/932807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931927] Re: [regression] Customized shortcuts don't work in compiz 1:0.9.7.0~bzr2995-0ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz-plugins-main (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931927 Title: [regression] Customized shortcuts don't work in compiz 1:0.9.7.0~bzr2995-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/931927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 926855] Re: [ARMhf] gcc produces assembler it can't compile
Hi Michael, I cant' find any asm chunks in there. (Only in some external declarations.) Can it look any other way? /Åsa On 15 February 2012 22:39, Michael Hope 926...@bugs.launchpad.net wrote: Asa, does the code contain any inline assembly? GCC estimates the size of each instruction and uses that to decide if it can use a short or a long branch. Long chunks of inline assembly can break that and make it think the code is shorter than it is. -- You received this bug notification because you are a member of Linaro Toolchain Developers, which is subscribed to Linaro GCC. https://bugs.launchpad.net/bugs/926855 Title: [ARMhf] gcc produces assembler it can't compile Status in Linaro GCC: Triaged Status in “gcc-4.6” package in Ubuntu: Confirmed Bug description: I'm porting the sagemath software to ARM. I completed the port with ubuntu oneiric. I upgraded to (a snapshot of) precise, and now a single file in the whole project doesn't build anymore. Hence something has been broken from oneiric/armel to precise/armhf. The attached mp.c is a gcc -E version of the problematic file, so it allows to easily reproduce the issue without fuss : if you compile it with gcc -c -o mp.o mp.c -O3 -funroll-loops, then the assembler will find two cases of branch out of range. Other switch combinations don't give problems, and the same combination is ok on x86_64 for example. Ah, on precise the gcc version is the one of Fri, 20 Jan 2012 12:10:59 +100 uploaded by doko, and changelog Merge with debian. There's no problem giving more details or doing tests if you want. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc-linaro/+bug/926855/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926855 Title: [ARMhf] gcc produces assembler it can't compile To manage notifications about this bug go to: https://bugs.launchpad.net/gcc-linaro/+bug/926855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
