[Bug 1272948] Re: python cflags shouldn't be added to CFLAGS
** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: New = Triaged -- 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/1272948 Title: python cflags shouldn't be added to CFLAGS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1272948/+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
[Blueprint servercloud-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE - [dave-cheney] Backport fixes from 1.3 branch for the go tool: TODO + [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS - [james-page] Package go tool for use with gccgo: BLOCKED + [james-page] Package go tool for use with gccgo: DONE [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO Testing of juju-core of gccgo early in cycle: INPROGRESS Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED Update juju-core to 2.x release: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: DONE Split shared go dependencies from juju-core source package: TODO MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: MRE for juju-core: TODO -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS [james-page] Package go tool for use with gccgo: DONE [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO Testing of juju-core of gccgo early in cycle: INPROGRESS Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED - Update juju-core to 2.x release: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: DONE Split shared go dependencies from juju-core source package: TODO MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: + Update juju-core to next stable release: TODO MRE for juju-core: TODO -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS [james-page] Package go tool for use with gccgo: DONE [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO Testing of juju-core of gccgo early in cycle: INPROGRESS Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED Ensure no code duplication between gccgo and juju-core dependency bundle: DONE - Split shared go dependencies from juju-core source package: TODO MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: Update juju-core to next stable release: TODO MRE for juju-core: TODO + + Work items: + Split shared go dependencies from juju-core source package: TODO -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS [james-page] Package go tool for use with gccgo: DONE [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO - Testing of juju-core of gccgo early in cycle: INPROGRESS - Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED Ensure no code duplication between gccgo and juju-core dependency bundle: DONE MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: + Testing of juju-core of gccgo early in cycle: INPROGRESS Update juju-core to next stable release: TODO MRE for juju-core: TODO Work items: Split shared go dependencies from juju-core source package: TODO + Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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 993660] Re: package samba-common 2:3.5.8~dfsg-1ubuntu2.4 failed to install/upgrade: unable to open '/etc/dhcp3/dhclient-enter-hooks.d/samba.dpkg-new': Too many levels of symbolic links
I did something similar in order to preserve the dhcp3. rm /etc/dhcp3 mkdir /etc/dhcp3 ln -s /etc/dhcp/* /etc/dhcp3/ Then I could: apt-get update apt-get install samba samba-common ! Still thing this is a bug in samba / samba-common because I had to specify it explicitly. -- 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/993660 Title: package samba-common 2:3.5.8~dfsg-1ubuntu2.4 failed to install/upgrade: unable to open '/etc/dhcp3/dhclient-enter- hooks.d/samba.dpkg-new': Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/993660/+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
[Blueprint servercloud-1311-juju] Juju activities for Trusty
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.11: SRU for juju-core 1.16.3 into saucy: DONE Work items for ubuntu-13.12: [doko] Provide 4.8.2 backport in PPA for Juju developers not running Trusty: DONE Create juju-mongodb package from mongodb: DONE [racb] Enable mongodb (core) on arm64: DONE [james-page] Enable juju-mongodb on arm64 and ppc64el: DONE Work items for ubuntu-14.01: [dave-cheney] Compatibility work juju-core - gccgo: DONE [dave-cheney] Backport fixes from 1.3 branch for the go tool: DONE [mwhudson] chase iant re: getting gccgo fixes into gcc 4.8 branch: DONE [dave-cheney] Work with upstream juju-core devs to switch to gccgo, at least for CI and landing: INPROGRESS - [james-page] Package go tool for use with gccgo: DONE + [james-page] Package go tool for use with gccgo: INPROGRESS [james-page] Upload 1.17.0 release with gccgo and gc built binaries: DONE [sinzui] Testing with gccgo in upstream CI: TODO Ensure no code duplication between gccgo and juju-core dependency bundle: DONE MIR raise juju-mongodb: DONE MIR raise juju-core: DONE MIR juju-core dependencies: TODO Work items for ubuntu-14.02: Testing of juju-core of gccgo early in cycle: INPROGRESS Update juju-core to next stable release: TODO MRE for juju-core: TODO Work items: Split shared go dependencies from juju-core source package: TODO Enable mongodb (v8) on arm64 (arm64 enabled in juju-mongodb package): POSTPONED -- Juju activities for Trusty https://blueprints.launchpad.net/ubuntu/+spec/servercloud-1311-juju -- 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 1261452] Re: juju-core is unavailable for arm64
I've just uploaded gccgo-go to Ubuntu Trusty; this should build the go tool for all architectures using gccgo. Just needs an archive-admin to review and accept. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261452/+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 1272508] Re: will postfix 2.11 be packaged in time for trusty’s freeze
This isn't really a bug, but I suppose I can triage it as a bug to upgrade to 2.11. ** Summary changed: - will postfix 2.11 be packaged in time for trusty’s freeze + Please update postfix to 2.11 ** Changed in: postfix (Ubuntu) Status: New = Triaged ** Changed in: postfix (Ubuntu) Importance: Undecided = Wishlist ** Tags added: upgrade-software-version -- 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/1272508 Title: Please update postfix to 2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1272508/+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 1272591] Re: package mysql-server-5.5 5.5.35-0ubuntu0.13.10.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu. Specifically, it looks like you have another daemon listening on the required port, or otherwise have an unusual network configuration. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu. If you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1272591 Title: package mysql-server-5.5 5.5.35-0ubuntu0.13.10.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1272591/+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 1268906] Re: cpu soft lockup running kvm
Serge has just identified that the trigger for this bug is running kvm with '-net user': without this option, no issues. ** Changed in: qemu-kvm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Latest series of oopses running on a fully updated trusty system. ** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
Same problem running with -vnc :7 ** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1268906] Re: cpu soft lockup running kvm
To be clear, my host system is a 64-bit capable first-gen i7, but is actually running fully 32-bit. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1272775] Re: package slapd 2.4.31-1+nmu2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If this is indeed a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openldap (Ubuntu) Status: New = Incomplete -- 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/1272775 Title: package slapd 2.4.31-1+nmu2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1272775/+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 1268906] Re: cpu soft lockup running kvm
Latest trusty desktop image (dated 24 Jan) results in the oops when running with kvm as: $ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title: cpu soft lockup running kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+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 1273205] [NEW] /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Public bug reported: I created an LXC container with the current armhf cloud images on a Calxeda node. Due to /etc/init/ttyAMA0.conf, I get these lines written into the terminal every few seconds: 4init: ttyAMA0 main process (3035) terminated with status 1 4init: ttyAMA0 main process ended, respawning This makes working in a terminal rather hard and also clutters logs. Can the job please be fixed to only start up if there actually is a /dev/ttyAMA*? $ uname -a Linux trusty-cloud 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:18:34 UTC 2013 armv7l armv7l armv7l GNU/Linux $ ls -l /dev/ttyA* ls: cannot access /dev/ttyA*: No such file or directory ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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 1272788] Re: php-fpm service won't start: unknown job
Confirmed. Reproduced on both LXC and KVM (in order to eliminate any overlayfs issue). Rebooting does seem to fix the issue. It seems to me that upstart doesn't pick up /etc/init.d/php5-fpm.conf. Perhaps this is related to the conversion from a SysV init script to upstart job in the upgrade? Is the php5-fpm packaging doing something wrong here? Dimitri, even if a reboot fixes the issue, it shouldn't be required, right? ** Changed in: php5 (Ubuntu) Status: New = Confirmed ** Changed in: php5 (Ubuntu) Importance: Undecided = Medium ** Summary changed: - php-fpm service won't start: unknown job + php-fpm service does not automatically restart after upgrade -- 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/1272788 Title: php-fpm service does not automatically restart after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1272788/+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 1273202] [NEW] policyd-spf runs as nobody
Public bug reported: Postfix is configured to execute policyd-spf as nobody rather than under a separate user. This is bad practice and could be a security risk if nobody is used by multiple daemons. The attached patch fixes the problem only for people who install the package for the first time and will not work if you do an upgrade. A dedicated user account is already created during installation of postfix-policyd-spf-python (1.0-1). DistroRelease: Ubuntu 12.04.3 LTS Package: amavisd-new-postfix 2.6.5-0ubuntu3.2 ** Affects: amavisd-new (Ubuntu) Importance: Undecided Status: New ** Patch added: amavisd-new-postfix.postinst.patch https://bugs.launchpad.net/bugs/1273202/+attachment/3958897/+files/amavisd-new-postfix.postinst.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1273202 Title: policyd-spf runs as nobody To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1273202/+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 1273202] Re: policyd-spf runs as nobody
The attachment amavisd-new-postfix.postinst.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1273202 Title: policyd-spf runs as nobody To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1273202/+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 1268906] Re: cpu soft lockup running kvm
On my AMD laptop (x130e thinkpad) with a uptodate trusty amd64 install, I cannot reproduce this. After installing a 32-bit trusty image, I can in fact reproduce it: Jan 27 13:07:05 serge-ThinkPad-X130e kernel: [ 725.593411] kvm: zapping shadow pages for mmio generation wraparound Jan 27 13:07:19 serge-ThinkPad-X130e kernel: [ 740.100465] kvm [3887]: vcpu0 unhandled rdmsr: 0xc0010001 Jan 27 13:07:21 serge-ThinkPad-X130e kernel: [ 742.187275] usb 1-1: USB disconnect, device number 3 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524715] BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-i38:3889] Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524729] Modules linked in: usb_storage parport_pc ppdev joydev rfcomm bnep arc4 uvcvideo rtl8192ce videobuf2_vmalloc videobuf2_memops videobuf2_core videodev rtl_pci kvm_amd rtlwifi kvm rtl8192c_common mac80211 microcode snd_hda_codec_conexant btusb snd_hda_codec_hdmi radeon cfg80211 bluetooth thinkpad_acpi snd_hda_intel snd_hda_codec nvram snd_hwdep snd_seq_midi snd_pcm snd_seq_midi_event snd_rawmidi snd_seq ttm psmouse drm_kms_helper snd_seq_device sp5100_tco snd_page_alloc rtsx_pci_ms serio_raw memstick drm snd_timer i2c_piix4 k10temp wmi i2c_algo_bit snd soundcore video mac_hid lp parport rtsx_pci_sdmmc rtsx_pci atl1c ahci libahci Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524815] CPU: 0 PID: 3889 Comm: qemu-system-i38 Not tainted 3.13.0-5-generic #20-Ubuntu Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524820] Hardware name: LENOVO 062223U/062223U, BIOS 8RET52WW (1.15 ) 11/15/2011 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524825] task: edc78d00 ti: f63e6000 task.ti: f63e6000 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524830] EIP: 0060:[c10a9cac] EFLAGS: 0202 CPU: 0 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524840] EIP is at __srcu_read_lock+0x2c/0x50 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524845] EAX: f14e4024 EBX: ECX: f7bdddf0 EDX: Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524848] ESI: 0001 EDI: 0001 EBP: f63e7dec ESP: f63e7de4 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524852] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524856] CR0: 8005003b CR2: CR3: 35e58000 CR4: 07f0 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524860] Stack: Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524863] f626b550 f63e7e6c f91da2f6 00b2 f7bd3400 57c83df4 134d36c2 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524873] f7bd3140 edc78d00 0046 edc78d00 f626b550 003e7e24 c1058fb7 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524882] f63e7e30 c164c598 f626b570 f63e7e94 c1644fac f626b570 360df2c8 f14e2008 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524892] Call Trace: Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524933] [f91da2f6] vcpu_enter_guest+0x636/0xc90 [kvm] Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524941] [c1058fb7] ? irq_exit+0x47/0xa0 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524950] [c164c598] ? smp_apic_timer_interrupt+0x38/0x50 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524957] [c1644fac] ? apic_timer_interrupt+0x34/0x3c Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.524988] [f91de0bf] kvm_arch_vcpu_ioctl_run+0x1cf/0x3e0 [kvm] Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525011] [f91ca0f3] kvm_vcpu_ioctl+0x433/0x4d0 [kvm] Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525019] [c1039eeb] ? lapic_next_event+0x1b/0x20 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525025] [c10b6315] ? clockevents_program_event+0x95/0x130 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525031] [c10b7989] ? tick_program_event+0x29/0x30 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525036] [c1076002] ? hrtimer_interrupt+0x142/0x2b0 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525042] [c1039eeb] ? lapic_next_event+0x1b/0x20 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525064] [f91c9cc0] ? vcpu_put+0x30/0x30 [kvm] Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525071] [c1185ee2] do_vfs_ioctl+0x2e2/0x4d0 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525078] [c10b0258] ? ktime_get_ts+0x48/0x140 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525083] [c1186130] SyS_ioctl+0x60/0x80 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525088] [c164bdcd] sysenter_do_call+0x12/0x28 Jan 27 13:07:48 serge-ThinkPad-X130e kernel: [ 768.525091] Code: 89 e5 56 53 3e 8d 74 26 00 8b 10 83 e2 01 8b 48 04 64 03 0d 04 d1 a6 c1 8d 1c 95 00 00 00 00 01 d9 8b 31 83 c6 01 89 31 0f ae f0 89 f6 8b 40 04 64 03 05 04 d1 a6 c1 01 d8 8b 48 08 83 c1 01 89 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1268906 Title:
[Bug 1273225] [NEW] php5enmod - priority is not set by argument
Public bug reported: Problem: While trying to enable a simple mod the priority parameter is not working: Step to reproduce: php5enmod apache2 tweaks/99 Expactation /etc/php5/apache2/conf.d/99-tweaks.ini Current result: /etc/php5/apache2/conf.d/20-tweaks.ini Affected version: trusty ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - php5endmod - priority is not set by argument + php5enmod - priority is not set by argument -- 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/1273225 Title: php5enmod - priority is not set by argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1273225/+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 1237364] Re: Commissioning with a Saucy image sets node status to Failed tests
We ran into this issue on 14.04. maas version: 1.4+bzr1820+dfsg-0ubuntu1 deploy 12.04.3 images Error output failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality) list xmlns:lldp=lldp xmlns:lshw=lshw lshw:node id=b7t6c claimed=true class=system handle=DMI:0001 lshw:descriptionDesktop Computer/lshw:description lshw:product(To be filled by O.E.M.)/lshw:product lshw:width units=bits64/lshw:width lshw:configuration lshw:setting id=boot value=normal/ lshw:setting id=chassis value=desktop/ lshw:setting id=family value=To be filled by O.E.M./ lshw:setting id=sku value=To be filled by O.E.M./ lshw:setting id=uuid value=007B4B0B-D534-E111-832F-ECA86BFE1858/ /lshw:configuration lshw:capabilities lshw:capability id=smbios-2.7SMBIOS version 2.7/lshw:capability lshw:capability id=dmi-2.7DMI version 2.7/lshw:capability lshw:capability id=vsyscall3232-bit processes/lshw:capability /lshw:capabilities lshw:node id=core claimed=true class=bus handle=DMI:0002 lshw:descriptionMotherboard/lshw:description lshw:productD53427RKE/lshw:product lshw:vendorIntel Corporation/lshw:vendor lshw:physid0/lshw:physid lshw:versionG87790-403/lshw:version lshw:serialGERK34400GZZ/lshw:serial lshw:slotTo be filled by O.E.M./lshw:slot lshw:node id=firmware claimed=true class=memory handle= lshw:descriptionBIOS/lshw:description lshw:vendorIntel Corp./lshw:vendor lshw:physid0/lshw:physid lshw:versionRKPPT10H.86A.0017.2013.0425.1251/lshw:version lshw:date04/25/2013/lshw:date lshw:size units=bytes65536/lshw:size lshw:capacity units=bytes16711680/lshw:capacity lshw:capabilities lshw:capability id=pciPCI bus/lshw:capability lshw:capability id=upgradeBIOS EEPROM can be upgraded/lshw:capability lshw:capability id=shadowingBIOS shadowing/lshw:capability lshw:capability id=cdbootBooting from CD-ROM/DVD/lshw:capability lshw:capability id=bootselectSelectable boot path/lshw:capability lshw:capability id=eddEnhanced Disk Drive extensions/lshw:capability lshw:capability id=int13floppy12005.25 1.2MB floppy/lshw:capability lshw:capability id=int13floppy7203.5 720KB floppy/lshw:capability lshw:capability id=int13floppy28803.5 2.88MB floppy/lshw:capability lshw:capability id=int5printscreenPrint Screen key/lshw:capability lshw:capability id=int14serialINT14 serial line control/lshw:capability lshw:capability id=int17printerINT17 printer control/lshw:capability lshw:capability id=acpiACPI/lshw:capability lshw:capability id=usbUSB legacy emulation/lshw:capability lshw:capability id=biosbootspecificationBIOS boot specification/lshw:capability /lshw:capabilities /lshw:node lshw:node id=cache:0 claimed=true class=memory handle=DMI:003D lshw:descriptionL2 cache/lshw:description lshw:physid3d/lshw:physid lshw:slotCPU Internal L2/lshw:slot lshw:size units=bytes524288/lshw:size lshw:capacity units=bytes524288/lshw:capacity lshw:capabilities lshw:capability id=internalInternal/lshw:capability lshw:capability id=write-throughWrite-trough/lshw:capability lshw:capability id=unifiedUnified cache/lshw:capability /lshw:capabilities /lshw:node lshw:node id=cache:1 claimed=true class=memory handle=DMI:003E lshw:descriptionL1 cache/lshw:description lshw:physid3e/lshw:physid lshw:slotCPU Internal L1/lshw:slot lshw:size units=bytes131072/lshw:size lshw:capacity units=bytes131072/lshw:capacity lshw:capabilities lshw:capability id=internalInternal/lshw:capability lshw:capability id=write-throughWrite-trough/lshw:capability lshw:capability id=dataData cache/lshw:capability /lshw:capabilities /lshw:node lshw:node id=cache:2 claimed=true class=memory handle=DMI:003F lshw:descriptionL3 cache/lshw:description lshw:physid3f/lshw:physid lshw:slotCPU Internal L3/lshw:slot lshw:size units=bytes3145728/lshw:size lshw:capacity units=bytes3145728/lshw:capacity lshw:capabilities lshw:capability id=internalInternal/lshw:capability lshw:capability id=write-backWrite-back/lshw:capability lshw:capability id=unifiedUnified cache/lshw:capability /lshw:capabilities /lshw:node lshw:node id=memory claimed=true class=memory handle=DMI:0040 lshw:descriptionSystem Memory/lshw:description lshw:physid40/lshw:physid lshw:slotSystem board or motherboard/lshw:slot lshw:size units=bytes17179869184/lshw:size lshw:node id=bank:0 claimed=true class=memory handle=DMI:0042 lshw:descriptionSODIMM DDR3 Synchronous 1600 MHz (0.6 ns)/lshw:description lshw:product9905428-087.A00LF/lshw:product lshw:vendorKingston/lshw:vendor lshw:physid0/lshw:physid lshw:serial2B130439/lshw:serial lshw:slotDIMM1/lshw:slot lshw:size units=bytes8589934592/lshw:size lshw:width
[Bug 1273225] Re: php5enmod - priority is not set by argument
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: php5 (Ubuntu) Status: New = Confirmed -- 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/1273225 Title: php5enmod - priority is not set by argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1273225/+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 1273225] Re: php5enmod - priority is not set by argument
Thank you for taking the time to report this bug and helping to make Ubuntu better. I don't see any code in php5-helper to support the module/priority syntax, though I can find references to it having been implemented by Ondřej back in 2012, and asking other packages to use it. It isn't clear to me whether this mechanism is still supported (and thus this is a bug), or if a different mechanism should now be used instead. It does look like setting priority inside the .ini file itself may work. I can't find any documentation inside source:php5 on using this or the syntax you used though. Ondřej, could you please comment? ** Changed in: php5 (Ubuntu) Status: Confirmed = Incomplete ** Changed in: php5 (Ubuntu) Importance: Undecided = Medium -- 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/1273225 Title: php5enmod - priority is not set by argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1273225/+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 1237364] Re: Commissioning with a Saucy image sets node status to Failed tests
The reason for the error is because node couldn't get to the Internet. Issue fixed by configuring the proxy to the MAAS server. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to Failed tests To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+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 1254931] Re: open-vm-tools-dkms 2013.09.16-1328054-0ubuntu2: open-vm-tools kernel module failed to build [error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’]
** Changed in: open-vm-tools (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1254931 Title: open-vm-tools-dkms 2013.09.16-1328054-0ubuntu2: open-vm-tools kernel module failed to build [error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1254931/+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 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
The problem can be mitigated by deleting /etc/init/ttyAMA0.conf or
editing to contain the following:
# ttyAMA0 - getty
#
# This service maintains a getty on ttyAMA0 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345] and (
not-container or
container CONTAINER=lxc or
container CONTAINER=lxc-libvirt)
stop on runlevel [!2345]
pre-start script
# getty will not be started if the serial console is not present
stty -F /dev/ttyAMA0 -a 2 /dev/null /dev/null || { stop ; exit 0; }
end script
respawn
script
exec /sbin/getty -L ttyAMA0 115200 vt102
end script
# written by cloud image build process
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Robert C Jennings (rcj)
** Changed in: cloud-init (Ubuntu)
Status: New = In Progress
** Changed in: cloud-init (Ubuntu)
Milestone: None = ubuntu-13.04-month-5
** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-13.04-month-5 = None
** Changed in: cloud-init (Ubuntu)
Milestone: None = raring-updates
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
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/1273205
Title:
/etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not
exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Martin, Can you confirm the contents of /etc/cloud/build.info? New cloud images have a test to make sure that this sort of thing shouldn't happen. Also I am a bit concerned that this might be an issue with upstart determiniing if its in a container. The previous version should have prevented the job from running within a container. -- 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/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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 1259592] Re: logcheck rules for ssh are not up to date
** Changed in: logcheck Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logcheck in Ubuntu. https://bugs.launchpad.net/bugs/1259592 Title: logcheck rules for ssh are not up to date To manage notifications about this bug go to: https://bugs.launchpad.net/logcheck/+bug/1259592/+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 1257732] Re: Wrong configuration file path in Mellanox Neutron Agent init script
This bug was fixed in the package neutron - 1:2014.1~b2-0ubuntu2 --- neutron (1:2014.1~b2-0ubuntu2) trusty; urgency=medium * debian/patches/skip-lb-test.patch: Skipped lb configuration test. -- Chuck Short zul...@ubuntu.com Mon, 27 Jan 2014 12:01:50 -0500 ** Changed in: neutron (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1257732 Title: Wrong configuration file path in Mellanox Neutron Agent init script To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1257732/+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 1249708] Re: Missing neutron-ovs-cleanup service
This bug was fixed in the package neutron - 1:2014.1~b2-0ubuntu2 --- neutron (1:2014.1~b2-0ubuntu2) trusty; urgency=medium * debian/patches/skip-lb-test.patch: Skipped lb configuration test. -- Chuck Short zul...@ubuntu.com Mon, 27 Jan 2014 12:01:50 -0500 ** Changed in: neutron (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1249708 Title: Missing neutron-ovs-cleanup service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1249708/+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 1243147] Re: Neutron ML2 plugin package is missing
This bug was fixed in the package neutron - 1:2014.1~b2-0ubuntu2 --- neutron (1:2014.1~b2-0ubuntu2) trusty; urgency=medium * debian/patches/skip-lb-test.patch: Skipped lb configuration test. -- Chuck Short zul...@ubuntu.com Mon, 27 Jan 2014 12:01:50 -0500 ** Changed in: neutron (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1243147 Title: Neutron ML2 plugin package is missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1243147/+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 251480] Re: X hangs in Intrepid in KVM
Hardy is EOL ** Changed in: kvm (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/251480 Title: X hangs in Intrepid in KVM To manage notifications about this bug go to: https://bugs.launchpad.net/kvm/+bug/251480/+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 1273429] [NEW] GNUCash won't open sqlite3 file due to libdbi
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1273407 Problem: Gnucash refuses to open a sqlite3 file (Fehlendes Dateimodul - missing file-module) Solution: downgrade to libdbi1 Version 0.8.4-6 from saucy $ apt-cache policy gnucash gnucash: Installiert: 1:2.6.0-1 $ apt-cache policy libdbd-sqlite3 libdbd-sqlite3: Installiert: 0.8.3-1+s-5ubuntu1 $ apt-cache policy libdbi1 libdbi1: Installiert: 0.8.4-6 Installationskandidat: 0.9.0-1 ** Affects: libdbi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libdbi in Ubuntu. https://bugs.launchpad.net/bugs/1273429 Title: GNUCash won't open sqlite3 file due to libdbi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbi/+bug/1273429/+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 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
** Changed in: cloud-init (Ubuntu) Status: In Progress = Incomplete -- 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/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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 1273447] [NEW] samba sharing doesn't work on fresh Ubuntu 14.04 x64 build - net usershare add: cannot convert name Everyone to a SID. Access denied
Public bug reported: This is fresh build of Ubuntu Trusty Tahr (development branch) Tried right click on couple of folders and tried to share throught SMB, but got error 255 code. D ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: samba 2:4.0.13+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Jan 27 21:30:10 2014 InstallationDate: Installed on 2014-01-17 (10 days ago) InstallationMedia: It NmbdLog: SambaServerRegression: No SmbConfIncluded: Yes SmbLog: Failed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) WindowsFailedConnect: Yes ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1273447 Title: samba sharing doesn't work on fresh Ubuntu 14.04 x64 build - net usershare add: cannot convert name Everyone to a SID. Access denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1273447/+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 1261452] Re: juju-core is unavailable for arm64
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261452/+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 1273462] [NEW] Upstart job config and init.d script are incompatible with each other
Public bug reported: Description:Ubuntu 13.10 Release:13.10 mysql-server-5.5: Installed: 5.5.35-0ubuntu0.13.10.1 Candidate: 5.5.35-0ubuntu0.13.10.1 Version table: *** 5.5.35-0ubuntu0.13.10.1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.5.32-0ubuntu7 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages In Ubuntu 13.10, the Upstart job and the init.d script do not work properly. In previous versions, the init.d script was a symlink to the wrapper script around upstart (/lib/init/upstart-job). This conflict means that if the server was started using the init.d script, upstart does not recognize that the server is running and will attempt to start a second instance of mysqld. Also problematic is that if the upstart job is started using the service or start commands, the init.d script's stop function runs a mysql shutdown, but upstart simply restarts mysqld (because it's marked respawn in the upstart config). ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: init scripts upstart -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1273462 Title: Upstart job config and init.d script are incompatible with each other To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+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 1261452] Re: juju-core is unavailable for arm64
This bug was fixed in the package juju-core - 1.17.0-0ubuntu3 --- juju-core (1.17.0-0ubuntu3) trusty; urgency=medium * Enable support for architectures other than x86/armhf (LP: #1261452): - d/control: Add BD on gccgo-go for archs that don't have golang-go, limit use of golang-go to supported archs only. -- James Page james.p...@ubuntu.com Mon, 27 Jan 2014 21:55:12 + ** Changed in: juju-core (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261452/+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 1271000] Re: lxc-start fails with Out of memory reading cgroups
Correct. It appears the default template processing (default meaning no template specified) seems like it could use a bit of work. Seems like specifying no template should either throw an error or create some form of container that will start. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+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 1273484] [NEW] nagios-plugins renamed to monitoring-plugins
Public bug reported: This project was forced to change its name because of a trademark assertion (see https://www.monitoring-plugins.org/news/new-project- name.html), so the package name, upstream URL in the package description, and possibly other references to the old name will need to be updated. See Debian Bug #736331 http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=736331 and Red Hat Bug #1054340 https://bugzilla.redhat.com/show_bug.cgi?id=1054340 for more details and discussion. Changes to file paths might be appropriate, but would break several things, so some discussion about that will be needed, possibly with some symlinks for a few releases or some such. I expect the details are best worked out upstream in Debian rather than creating a delta, but it seems like we need a bug report on Ubuntu as well since changes may need to happen before the Trusty release, particularly since it's LTS. This affects all versions of Ubuntu at this point, but it's probably most sane to only change things for Trusty and releases after that at this point, IMO. Upgrades from previous releases to Trusty or later should replace the old package with the new name (the Red Hat bug has lots of discussion about upgrade paths - it may be worthwhile to talk with Sam Kottler so Ubuntu/Debian end up with similar behavior to Red Hat/CentOS/Fedora in this respect). This also affects the dependencies of several other packages, such as nagios3-common, icinga-common, shinken-common, and probably others. ** Affects: nagios-plugins (Ubuntu) Importance: Undecided Status: New ** Affects: nagios-plugins (Debian) Importance: Unknown Status: Unknown ** Affects: nagios-plugins (Fedora) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #736331 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736331 ** Also affects: nagios-plugins (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736331 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1054340 https://bugzilla.redhat.com/show_bug.cgi?id=1054340 ** Also affects: nagios-plugins (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1054340 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1273484 Title: nagios-plugins renamed to monitoring-plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1273484/+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 1273197] Re: maas-cluster-controller does not update pserv.yaml when dpkg-reconfigure is run
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1273197 Title: maas-cluster-controller does not update pserv.yaml when dpkg- reconfigure is run To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1273197/+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 1273484] Re: nagios-plugins renamed to monitoring-plugins
** Changed in: nagios-plugins (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1273484 Title: nagios-plugins renamed to monitoring-plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1273484/+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 1273494] Re: When installing MAAS, the administrator should be presented with a choice to automatically configure the hosts nameserver to point to the MAAS DNS server.
** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1273494 Title: When installing MAAS, the administrator should be presented with a choice to automatically configure the hosts nameserver to point to the MAAS DNS server. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1273494/+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 1261452] Re: juju-core is unavailable for arm64
juju-core 1.17.0-0ubuntu3 timed out building, but it looks like a kernel issue. I reproduced this hang on both a 3.8 and a 3.12 kernel. However, I tested w/ a 3.13 (hand rolled w/ xgene support), and juju-core built fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261452 Title: juju-core is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1261452/+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 963142] Re: kernel BUG at /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.c:392!
[Expired for iscsitarget (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iscsitarget (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/963142 Title: kernel BUG at /var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.c:392! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/963142/+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 1180281] Re: “Unable to connect to libvirt” when using virt-manager with the xl toolstack and Xen 4.2.1
This problem still affects Ubuntu 14.04 (devel branch). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1180281 Title: “Unable to connect to libvirt” when using virt-manager with the xl toolstack and Xen 4.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281/+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 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Ah, thanks for pointing out /etc/cloud/build.info. In said chroot that says build_name: server serial: 20131219.1 Note that I created this container last Thursday (2014-01-23), I already wondered why there were a gazillion packages to dist-upgrade right after I created it with sudo lxc-create -t ubuntu-cloud -n trusty-cloud -- -r trusty but I created that on saucy, with trusty's cloud-image-utils (as saucy's doesn't find the armhf images). Perhaps that was the reason why it picked up an ancient cloud image. Is it possible to get a recent one with saucy's lxc-create, or should I upgrade the whole box to current trusty? -- 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/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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 1273205] Re: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist
Another observation: I still see these messages today after dist- upgrading to container to latest trusty. But *only* with lxc-start, *not* with lxc-start-ephemeral. In the latter case, the job still gets started: $ sudo status ttyAMA0 ttyAMA0 start/running, process 769 but I don't see the spewage. With ps aux|grep ttyAMA I still see the job constantly being respawned, but it doesn't appear at the terminal any more (that might be an LXC quirk/feature/bug, probably unrelated to the cloud image itself). -- 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/1273205 Title: /etc/init/ttyAMA0.conf causes endless tty spewage if ttyAMA does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1273205/+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
