[Bug 1298280] Re: Update OpenSSH to 6.6
This bug was fixed in the package openssh - 1:6.6p1-1 --- openssh (1:6.6p1-1) unstable; urgency=medium [ Colin Watson ] * Apply various warning-suppression and regression-test fixes to gssapi.patch from Damien Miller. * New upstream release (http://www.openssh.com/txt/release-6.6, LP: #1298280): - CVE-2014-2532: sshd(8): when using environment passing with an sshd_config(5) AcceptEnv pattern with a wildcard, OpenSSH prior to 6.6 could be tricked into accepting any environment variable that contains the characters before the wildcard character. * Re-enable btmp logging, as its permissions were fixed a long time ago in response to #370050 (closes: #341883). * Change to PermitRootLogin without-password for new installations, and ask a debconf question when upgrading systems with PermitRootLogin yes from previous versions (closes: #298138). * Debconf translations: - Danish (thanks, Joe Hansen). - Portuguese (thanks, Américo Monteiro). - Russian (thanks, Yuri Kozlov; closes: #742308). - Swedish (thanks, Andreas Rönnquist). - Japanese (thanks, victory). - German (thanks, Stephan Beck; closes: #742541). - Italian (thanks, Beatrice Torracca). * Don't start ssh-agent from the Upstart user session job if something like Xsession has already done so (based on work by Bruno Vasselle; LP: #1244736). [ Matthew Vernon ] * CVE-2014-2653: Fix failure to check SSHFP records if server presents a certificate (bug reported by me, patch by upstream's Damien Miller; thanks also to Mark Wooding for his help in fixing this) (Closes: #742513) -- Colin Watson cjwat...@debian.org Fri, 28 Mar 2014 18:04:41 + ** Changed in: openssh (Ubuntu) Status: Fix Committed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-2532 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-2653 -- 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/1298280 Title: Update OpenSSH to 6.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1298280/+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 1244736] Re: upstart configuration for user launches an extra ssh-agent
This bug was fixed in the package openssh - 1:6.6p1-1 --- openssh (1:6.6p1-1) unstable; urgency=medium [ Colin Watson ] * Apply various warning-suppression and regression-test fixes to gssapi.patch from Damien Miller. * New upstream release (http://www.openssh.com/txt/release-6.6, LP: #1298280): - CVE-2014-2532: sshd(8): when using environment passing with an sshd_config(5) AcceptEnv pattern with a wildcard, OpenSSH prior to 6.6 could be tricked into accepting any environment variable that contains the characters before the wildcard character. * Re-enable btmp logging, as its permissions were fixed a long time ago in response to #370050 (closes: #341883). * Change to PermitRootLogin without-password for new installations, and ask a debconf question when upgrading systems with PermitRootLogin yes from previous versions (closes: #298138). * Debconf translations: - Danish (thanks, Joe Hansen). - Portuguese (thanks, Américo Monteiro). - Russian (thanks, Yuri Kozlov; closes: #742308). - Swedish (thanks, Andreas Rönnquist). - Japanese (thanks, victory). - German (thanks, Stephan Beck; closes: #742541). - Italian (thanks, Beatrice Torracca). * Don't start ssh-agent from the Upstart user session job if something like Xsession has already done so (based on work by Bruno Vasselle; LP: #1244736). [ Matthew Vernon ] * CVE-2014-2653: Fix failure to check SSHFP records if server presents a certificate (bug reported by me, patch by upstream's Damien Miller; thanks also to Mark Wooding for his help in fixing this) (Closes: #742513) -- Colin Watson cjwat...@debian.org Fri, 28 Mar 2014 18:04:41 + ** Changed in: openssh (Ubuntu) Status: Confirmed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-2532 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-2653 -- 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/1244736 Title: upstart configuration for user launches an extra ssh-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1244736/+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 1299588] Re: LXC permission denied issue with 1.17.7
** Tags added: micro-cluster -- 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/1299588 Title: LXC permission denied issue with 1.17.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1299588/+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 1299588] Re: LXC permission denied issue with 1.17.7
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: juju-core (Ubuntu) Status: New = Confirmed -- 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/1299588 Title: LXC permission denied issue with 1.17.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1299588/+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 945433] Re: Incorrect GPT length should be handled better
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdisk (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/945433 Title: Incorrect GPT length should be handled better To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/945433/+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 945433] Re: Incorrect GPT length should be handled better
This bug is causing Ubuntu Ubiquity installer to crash. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/945433 Title: Incorrect GPT length should be handled better To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/945433/+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 1297077] Re: juju-local should depend on cpu-checker
** Changed in: juju-core Assignee: (unassigned) = Curtis Hovey (sinzui) ** Changed in: juju-core Milestone: None = 1.18.0 -- 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/1297077 Title: juju-local should depend on cpu-checker To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1297077/+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 1295892] Re: nginx upgrade failed
Seth, I'll take a poke at this, in a little while, I have to spin up a 13.10 VM for testing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1295892 Title: nginx upgrade failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1295892/+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 1297077] Re: juju-local should depend on cpu-checker
** Changed in: juju-core Status: Triaged = Fix Committed -- 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/1297077 Title: juju-local should depend on cpu-checker To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1297077/+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 1294267] Re: tgt doesn't export some LUNs after a reload operation (SIGHUP)
Hi Serge Hallyn,
I run some new tests and, in short, the problem I found is actually three
problems (maybe this bug should be broke in three).
I will summarize the problems I found:
- Tgtd breaks when it receives a SIGHUP;
- When we send a SIGHUP to tgtd (`reload tgt`), the deamon stops (and it logs
an fault in syslog), and then upstart respawns the deamon. It is, run `reload
tgt` appears to be equivalent to run `kill -9 TGT_ROOT_PID; start tgt;`;
- Tgtd has an unexpected behavior when we run a `restart tgt` or a `stop tgt;
start tgt` command;
- When tgtd stops and closes the devices, the system will probably run a
`blkid` in this devices. So, when tgtd starts again, some devices may be still
opened by the blkid command, and neither tgtd or `tgt-admin -e` will add this
device (I'm considering allow-in-use is configured to off in this moment);
- The `stop tgt` command really stops tgtd even if some LUNs still in use;
- This can cause data corruption.
Debian wheezy (https://packages.debian.org/source/wheezy/tgt) solves
these problem using the initd.sample from upstream.
In the next explanations, I'm using the source code found in:
http://packages.ubuntu.com/source/precise/tgt
- Tgtd breaks when it receives a SIGHUP:
From the initd.sample file (tgt-1.0.17/scripts/initd.sample, line 79):
reload()
{
echo Updating target framework daemon configuration
# Update configuration for targets. Only targets which
# are not in use will be updated.
tgt-admin --update ALL -c $TGTD_CONFIG /dev/null
RETVAL=$?
if [ $RETVAL -eq 107 ] ; then
echo tgtd is not running
exit 1
fi
}
It is, the `service tgt reload` command will run a `tgt-admin --update
ALL` command, and this last command works fine. The `service tgt reload`
command DOESN'T send a SIGHUP signal in Debian (and in all Linux
distributions that uses the initd.sample file).
I don't see how fix this in Ubuntu using upstart, because in Ubuntu
12.04 Upstart always send a SIGHUP signal. In newer versions of Ubuntu
we can use the `reload signal` stanza, but we can't run a script (`tgt-
admin --update ALL`) when `reload tgt` was called.
- Tgtd has an unexpected behavior when we run a `restart tgt` or a `stop
tgt; start tgt` command:
First, let's read the tgt-admin source code (tgt-1.0.17/scripts/tgt-
admin, line 1240):
# Check if userspace uses this device
my $lsof_check = check_exe(lsof);
if ($lsof_check ne 1) {
system(lsof $backing_store /dev/null);
my $exit_value = $? 8;
if ($exit_value eq 0) {
execute(# Device $backing_store is used (already tgtd
target?).);
execute(# Run 'lsof $backing_store' to see the
details.);
return 0;
}
}
It is, when `tgt-admin -e` (in the `post-start` stanza) is executed, if
some device still opened (in our case, by the `blkid` command), we can
add this device as a LUN.
In my attachment tgt.override, a hack was proposed to avoid this
problem. However, my tests showed that waiting one second between stops
and starts tgtd solves the problem. Actually, 0.3 second waiting solved
my problem in all tests (but 1 second is a more secure interval).
From the initd.sample file (tgt-1.0.17/scripts/initd.sample, line 125):
restart)
TASK=restart
stop start
;;
And from line 19:
# Put tgtd into offline state until all the targets are configured.
# We don't want initiators to (re)connect and fail the connection
# if it's not ready.
tgtadm --op update --mode sys --name State -v offline
# Configure the targets.
tgt-admin -e -c $TGTD_CONFIG
# Put tgtd into ready state.
tgtadm --op update --mode sys --name State -v ready
A fix for this problem can be:
# Put tgtd into offline state until all the targets are configured.
# We don't want initiators to (re)connect and fail the connection
# if it's not ready.
tgtadm --op update --mode sys --name State -v offline
+ # Wait the system free the backing-stores (a `blkid` command
+ # may still be running)
+ # See: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1294267
+ [ $TASK == restart ] sleep 1
# Configure the targets.
tgt-admin -e -c $TGTD_CONFIG
# Put tgtd into ready state.
tgtadm --op update --mode sys --name State -v ready
- The `stop tgt` command really stops tgtd even if some LUNs still in
use:
Let's see the source code again (tgt-1.0.17/scripts/initd.sample, line
35):
# Remove all targets. It only removes targets which are not in use.
tgt-admin --update ALL -c /dev/null /dev/null
# tgtd will exit if all targets were removed
tgtadm --op delete --mode system /dev/null
RETVAL=$?
if
[Bug 1299186] Re: Creating a Samba Share is not possible because 'net usershare' returned error 255: net usershare add: cannot convert name Everyone to a SID. Access denied.
It renders essential functionality of the package (or a dependent one) broken. ** Changed in: samba (Ubuntu) Importance: Undecided = High -- 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/1299186 Title: Creating a Samba Share is not possible because 'net usershare' returned error 255: 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/1299186/+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 1295892] Re: nginx upgrade failed
Seth, I was unable to replicate this using the default configurations, are you running any other webservers on your system, or have any special listen statements in your configs? (This seems like a configuration problem on your setup rather than globally) ** Changed in: nginx (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1295892 Title: nginx upgrade failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1295892/+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 1257186] Re: memory leakage messages
PS: So that Google will find it, I'll post my exact message with a different (line?) number: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory HTH -- 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/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1257186] Re: memory leakage messages
I can confirm James Dupin's post: gone after sudo apt-get remove libpam-smbpass. See http://ubuntuforums.org/showthread.php?t=2214042 with my experience before I saw this post. -- 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/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1299926] [NEW] package ntp 1:4.2.6.p5+dfsg-3ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 13.10 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-18.12-lowlatency 3.11.10.4 Uname: Linux 3.11.0-18-lowlatency x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 00:20:58 2014 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück InstallationDate: Installed on 2014-03-30 (0 days ago) InstallationMedia: It MarkForUpload: True ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-lowlatency root=UUID=92db6600-df38-47b3-997a-504f998cbc28 ro quiet splash SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1299926 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1299926/+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 1299934] Re: package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
** Tags removed: need-duplicate-check -- 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/1299934 Title: package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299934/+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 1299944] [NEW] lxc-container-default-with-nesting is too lax
Public bug reported: Before cgmanager, lxc-container-default-with-nesting needed to allow the container to mount fstype=cgroup. This is no longer needed and is not safe, therefore should no longer be allowed. (This ignores the fact that proc and sys mounts under /var/cache/lxc allow bypassing proc restrictions currently) ** 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/1299944 Title: lxc-container-default-with-nesting is too lax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1299944/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
** Changed in: maas Milestone: None = 14.04 -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
** Changed in: maas Milestone: None = 14.04 -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+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 1234880] Re: HP ilo4 consoles default to autodetect protocol, which doesn't work
** Changed in: maas Milestone: None = 14.04 -- 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/1234880 Title: HP ilo4 consoles default to autodetect protocol, which doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1234880/+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 1289489] Re: Installing MAAS from cloud-tools-next on precise fails
** Changed in: maas Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1289489 Title: Installing MAAS from cloud-tools-next on precise fails To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1289489/+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 1299964] [NEW] make Ubuntu logo more Ubuntu-y
Public bug reported: The previous Ubuntu logo was white on aubergine. Really, this is Ubuntu, not Canonical, and we should be highlighting the Ubuntu orange. Also, in the prompt, we should use orange for the hostname and aubergine for the current working directory. ** Affects: byobu (Ubuntu) Importance: Wishlist Assignee: Dustin Kirkland (kirkland) Status: In Progress ** Changed in: byobu (Ubuntu) Importance: Undecided = Wishlist ** Changed in: byobu (Ubuntu) Status: New = In Progress ** Changed in: byobu (Ubuntu) Assignee: (unassigned) = Dustin Kirkland (kirkland) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1299964 Title: make Ubuntu logo more Ubuntu-y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1299964/+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 1299964] Re: make Ubuntu logo more Ubuntu-y
** Branch linked: lp:byobu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1299964 Title: make Ubuntu logo more Ubuntu-y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1299964/+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 1299972] [NEW] Default site config is ambiguous in PHP block (precise)
Public bug reported: In the default sites-available configuration file, it is ambiguous which line to use for PHP files in a proxy_pass. It also uses an incorrect configuration line for the PHP files. It may need modified to adapt for this so that php5-fpm+nginx setups work out of the box on the default configurations for Precise. -- I am marking this Triaged and Low because this is a low-priority bug and because this was initially reported to me in comments on Ask Ubuntu (see this comment: http://askubuntu.com/questions/134666/what-is-the- easiest-way-to-enable-php-on- nginx/134676?noredirect=1#comment576704_134676 ), and I have actually confirmed this to be the case. (see http://bazaar.launchpad.net /~ubuntu-branches/ubuntu/precise/nginx/precise- updates/view/head:/debian/conf/sites-available/default#L67 ) Fixing this is as simple as changing the configuration lines here so they have different comments on which line to use. ** Affects: nginx (Ubuntu) Importance: Low Status: Triaged ** Tags: precise ** Summary changed: - Precise default config ambiguous in PHP block + Default site config is ambiguous in PHP block (precise) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1299972 Title: Default site config is ambiguous in PHP block (precise) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1299972/+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 1299934] Re: package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
** Package changed: samba (Ubuntu) = debconf (Ubuntu) -- 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/1299934 Title: package samba-common 2:3.6.3-2ubuntu2.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1299934/+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 1299975] [NEW] wireless script checks wrong sys file
Public bug reported: On Trusty (beta), while trying to diagnose an issue with the wireless not connecting upon resume from standby, I discovered an invalid check in '/usr/lib/pm-utils/power.d/wireless'. The script checks '/sys/class/net/$1/device/enable' to see if the wireless device is enabled, failing to perform any configuration if this sys file does not exist. That happens to be the case for me (intel wireless), which the actual location is '/sys/class/net/$1/device/enabled' (enable - enabled). Changing the script to use the correct location has not fixed my wireless resume issue, but perhaps it is contributing to wireless issues for others. My wireless power-saving is correctly turned off upon resume now, though (it would get stuck in power-saving mode sometimes). $ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 $ apt-cache policy pm-utils pm-utils: Installed: 1.4.1-13 Candidate: 1.4.1-13 Version table: *** 1.4.1-13 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1299975 Title: wireless script checks wrong sys file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+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 1299989] [NEW] maas-dns fails to install without python-seamicroclient
You have been subscribed to a public bug:
I'm reporting the symptom, but I think more fundamentally it means that
a maas-region-admin invocation in the packaging scripts for maas-dns
creates an implicit back-dependency on maas-region-controller. Maybe
it's an invocation that can simply be skipped if maas-region-controller
is not present.
Here's what I get while installing prerequisites for maas-region-
controller, but not yet maas-region-controller itself, on an up-to-date
Trusty system as of 2014-03-31:
Setting up maas-dns (1.5+bzr2203+2205+257~ppa0~ubuntu14.04.1) ...
Traceback (most recent call last):
File /usr/bin/django-admin, line 5, in module
management.execute_from_command_line()
File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py,
line 399, in execute_from_command_line
utility.execute()
File /usr/lib/python2.7/dist-packages/django/core/management/__init__.py,
line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
242, in run_from_argv
self.execute(*args, **options.__dict__)
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
284, in execute
self.validate()
File /usr/lib/python2.7/dist-packages/django/core/management/base.py, line
310, in validate
num_errors = get_validation_errors(s, app)
File /usr/lib/python2.7/dist-packages/django/core/management/validation.py,
line 34, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line
196, in get_app_errors
self._populate()
File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 78,
in _populate
self.load_app(app_name)
File /usr/lib/python2.7/dist-packages/django/db/models/loading.py, line 99,
in load_app
models = import_module('%s.models' % app_name)
File /usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40,
in import_module
__import__(name)
File /usr/lib/python2.7/dist-packages/maasserver/models/__init__.py, line
44, in module
from maasserver.models.bootimage import BootImage
File /usr/lib/python2.7/dist-packages/maasserver/models/bootimage.py, line
26, in module
from maasserver.models.nodegroup import NodeGroup
File /usr/lib/python2.7/dist-packages/maasserver/models/nodegroup.py, line
35, in module
from maasserver.refresh_worker import refresh_worker
File /usr/lib/python2.7/dist-packages/maasserver/refresh_worker.py, line
21, in module
from provisioningserver.tasks import refresh_secrets
File /usr/lib/python2.7/dist-packages/provisioningserver/tasks.py, line 45,
in module
from provisioningserver.custom_hardware.seamicro import (
File
/usr/lib/python2.7/dist-packages/provisioningserver/custom_hardware/seamicro.py,
line 27, in module
from seamicroclient import (
ImportError: No module named seamicroclient
dpkg: error processing package maas-dns (--configure):
subprocess installed post-installation script returned error exit status 1
** Affects: maas (Ubuntu)
Importance: Critical
Status: Triaged
--
maas-dns fails to install without python-seamicroclient
https://bugs.launchpad.net/bugs/1299989
You received this bug notification because you are a member of Ubuntu Server
Team, which is subscribed to maas in Ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1299989] Re: maas-dns fails to install without python-seamicroclient
** Project changed: maas = maas (Ubuntu) ** Changed in: maas (Ubuntu) Milestone: 14.04 = None -- 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/1299989 Title: maas-dns fails to install without python-seamicroclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1299989/+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 1300010] Re: Ubuntu12.04.4(LTS)--icehouse-apt-get heat packaging issues
** Project changed: openstack-manuals = heat (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heat in Ubuntu. https://bugs.launchpad.net/bugs/1300010 Title: Ubuntu12.04.4(LTS)--icehouse-apt-get heat packaging issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1300010/+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
