[Bug 903752] Re: [MIR] sssd
alrighty, the transition is now done and 1.11.2-1 built against the new samba, so seeding it should succeed now -- 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/libsemanage/+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 1175028] Re: Mongodb links GPL code with SSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libmongodb-perl (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1175028 Title: Mongodb links GPL code with SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmongodb-perl/+bug/1175028/+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 1175028] Re: Mongodb links GPL code with SSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libmongodb-perl (Ubuntu Saucy) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1175028 Title: Mongodb links GPL code with SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmongodb-perl/+bug/1175028/+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 1175028] Re: Mongodb links GPL code with SSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libmongodb-perl (Ubuntu Raring) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1175028 Title: Mongodb links GPL code with SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmongodb-perl/+bug/1175028/+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 997978] Re: KVM images lose connectivity with bridged network
I have to clarify that I'm not sure that this has something to do with KVM, QEMU and the like. I think is more a problem of the linux bridge driver since It fails even if you don't have any vm running. Yes, it takes more time to fail but this can be because not enough traffic to make it fail. -- 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/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+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 1246482] Re: Documentation needs to cover configuring MAAS for tftp boot
I presume documentation is addressed in the upstream project? ** Package changed: maas (Ubuntu) = maas ** Summary changed: - Documentation needs to cover configuring MAAS for tftp boot + Documentation does not cover configuring MAAS for tftp boot -- 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/1246482 Title: Documentation does not cover configuring MAAS for tftp boot To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1246482/+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 390730] Re: mdb-export prints binary for OLE fields.
** Changed in: mdbtools (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mdbtools in Ubuntu. https://bugs.launchpad.net/bugs/390730 Title: mdb-export prints binary for OLE fields. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdbtools/+bug/390730/+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 1227033] Re: mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal()
** Changed in: mdbtools (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mdbtools in Ubuntu. https://bugs.launchpad.net/bugs/1227033 Title: mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdbtools/+bug/1227033/+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: Drafter: James Page = Ubuntu Server Team -- 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: INPROGRESS Work items for ubuntu-13.12: - Create juju-mongodb package from mongodb: TODO + Create juju-mongodb package from mongodb: INPROGRESS [racb] Enable mongodb/libv8 on arm64: TODO Completion of juju-core updates for gccgo compatibility: TODO Testing with gccgo in upstream CI: TODO Testing of juju-core of gccgo early in cycle: TODO Work items for ubuntu-14.01: Update juju-core to 2.x release: TODO Split shared go dependencies from juju-core source package: TODO MIR juju-mongodb: TODO MIR juju-core: TODO MIR juju-core dependencies: TODO Work items for ubuntu-14.04: 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: Assignee: Ubuntu Server Team = James Page -- 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 1208430] Re: mongodb runs as root user
** Changed in: juju-core (Ubuntu) Importance: Medium = High -- 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/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+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 1255927] Re: package mysql-server-5.5 (not installed) failed to install/upgrade: 子进程 新的 pre-installation 脚本 返回了错误号 1
Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu. 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/1255927 Title: package mysql-server-5.5 (not installed) failed to install/upgrade: 子进程 新的 pre-installation 脚本 返回了错误号 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1255927/+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 1242237] Re: Mongodb server ignores --smallfiles if other paramethers are set in the command line
** Changed in: mongodb (Ubuntu) Importance: Undecided = Low ** Changed in: mongodb (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1242237 Title: Mongodb server ignores --smallfiles if other paramethers are set in the command line To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1242237/+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 1224910] Re: Error! Build of vmblock.ko failed for: 3.8.0-30-generic (x86_64)
*** This bug is a duplicate of bug 1083719 *** https://bugs.launchpad.net/bugs/1083719 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: open-vm-tools (Ubuntu) Status: New = Confirmed -- 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/1224910 Title: Error! Build of vmblock.ko failed for: 3.8.0-30-generic (x86_64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1224910/+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 1251939] Re: Chroot fails with Cannot chroot when not started as root error
As 2.4.6-4 hasn't been uploaded to Debian yet, and fixing Trusty blocks fixing Saucy, I've verified the problem with a dep8 test, verified Stefan's patch with it and uploaded the fix to Trusty. Thanks! ** Changed in: apache2 (Ubuntu) Status: Triaged = Fix Committed ** Also affects: apache2 (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu Saucy) Status: New = Triaged ** Changed in: apache2 (Ubuntu Saucy) Importance: Undecided = Medium -- 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/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 1251939] Re: Chroot fails with Cannot chroot when not started as root error
** Description changed: + [Impact] + + The Apache ChrootDir doesn't work, causing Apache to fail if you try to + use it. This means that it is not possible to run Apache in a chroot, + which is a regression from 13.04. + + [Development Fix] + + Adjust build system to not use things inside .pc/. This also requires + the regeneration of debian/patches/itk-rerun-configure.patch. + + [Stable Fix] + + Same as development fix. + + [Test Case] + + In included dep8 test. Install dpkg-dev and wget, then run sh + debian/tests/chroot. This requires root, and will clobber your Apache + installation, so do this only on a fresh install that you can throw away + afterwards. + + [Regression Potential] + + Having to adjust the build system is not ideal, and could impact + anything. But what was being done before is obviously flawed, and could + introduce other problems not yet reported. + + On balance, I think it is worth the SRU, since the unknowns also include + other bugs that we don't know about. + + It might be worth mandating additional verification here, though, or a + longer than normal aging period. + + I will leave the SRU team to decide. + + [Original Description] + I have set my chroot directory as shown below. ChrootDir /var/www When started with the above chroot setting, apache2 exits with the following error [Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical result out of range: AH02158: Cannot chroot when not started as root NOTE: apache2 is started as 'root' user. This was reported as a bug in apache.org earlier (link below) where it was confirmed this is fixed in a trunk. https://issues.apache.org/bugzilla/show_bug.cgi?id=55787 Details of my Ubuntu server: - - root@gorilla:~# cat /etc/lsb-release + root@gorilla:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 root@gorilla:~# apache2ctl -v Server version: Apache/2.4.6 (Ubuntu) Server built: Aug 9 2013 14:31:04 root@gorilla:~# apache2ctl -l -M Compiled in modules: - core.c - mod_so.c - mod_watchdog.c - http_core.c - mod_log_config.c - mod_logio.c - mod_version.c - mod_unixd.c - mod_unixd.c + core.c + mod_so.c + mod_watchdog.c + http_core.c + mod_log_config.c + mod_logio.c + mod_version.c + mod_unixd.c + mod_unixd.c ** Description changed: [Impact] - The Apache ChrootDir doesn't work, causing Apache to fail if you try to - use it. This means that it is not possible to run Apache in a chroot, - which is a regression from 13.04. + The Apache ChrootDir directive doesn't work, causing Apache to fail if + you try to use it. This means that it is not possible to run Apache in a + chroot, which is a regression from 13.04. [Development Fix] Adjust build system to not use things inside .pc/. This also requires the regeneration of debian/patches/itk-rerun-configure.patch. [Stable Fix] Same as development fix. [Test Case] In included dep8 test. Install dpkg-dev and wget, then run sh debian/tests/chroot. This requires root, and will clobber your Apache installation, so do this only on a fresh install that you can throw away afterwards. [Regression Potential] Having to adjust the build system is not ideal, and could impact anything. But what was being done before is obviously flawed, and could introduce other problems not yet reported. On balance, I think it is worth the SRU, since the unknowns also include other bugs that we don't know about. It might be worth mandating additional verification here, though, or a longer than normal aging period. I will leave the SRU team to decide. [Original Description] I have set my chroot directory as shown below. ChrootDir /var/www When started with the above chroot setting, apache2 exits with the following error [Sat Nov 16 13:52:40.621872 2013] [unixd:alert] [pid 3747] (34)Numerical result out of range: AH02158: Cannot chroot when not started as root NOTE: apache2 is started as 'root' user. This was reported as a bug in apache.org earlier (link below) where it was confirmed this is fixed in a trunk. https://issues.apache.org/bugzilla/show_bug.cgi?id=55787 Details of my Ubuntu server: - root@gorilla:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION=Ubuntu 13.10 root@gorilla:~# apache2ctl -v Server version: Apache/2.4.6 (Ubuntu) Server built: Aug 9 2013 14:31:04 root@gorilla:~# apache2ctl -l -M Compiled in modules: core.c mod_so.c mod_watchdog.c http_core.c mod_log_config.c mod_logio.c mod_version.c mod_unixd.c mod_unixd.c -- You received this bug notification because you are a member of
[Bug 1251939] Re: Chroot fails with Cannot chroot when not started as root error
This bug was fixed in the package apache2 - 2.4.6-2ubuntu4 --- apache2 (2.4.6-2ubuntu4) trusty; urgency=low * d/p/ignore-quilt-dir, d/p/itk-rerun-configure.patch: adjust build system so that it does not use files find inside the .pc directory. This stops a double module load causing later havoc, including ChrootDir directive failure (LP: #1251939). Thanks to Stefan Fritsch. * d/tests/chroot: dep8 test for ChrootDir case. -- Robie Basak robie.ba...@ubuntu.com Thu, 28 Nov 2013 16:21:51 + ** Changed in: apache2 (Ubuntu) Status: Fix Committed = 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/1251939 Title: Chroot fails with Cannot chroot when not started as root error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 1256087] [NEW] package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: This bug happens since 13.04. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: spamassassin (not installed) ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 28 20:28:50 2013 DuplicateSignature: package:spamassassin:(not installed):le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2013-05-25 (187 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: spamassassin Title: package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to saucy on 2013-10-19 (40 days ago) ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1256087 Title: package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1256087/+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 1256087] Re: package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
I just removed Spamassassin --purge. Sould'nt report error anymore! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1256087 Title: package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1256087/+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 1256087] Re: package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1256087 Title: package spamassassin (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1256087/+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
