to the search terms in the search-box. If the
search-box is made empty in the new tab you have to retype your entire
search query out again.
(In reply to Greg from comment #81)
I vote against this. Search-box should NOT be tab specific.
If you open a new tab and then tap CTRL+K and start typing
Another reason to keep the old search query in the search box in a new
tab is if you want to perform the same search with a different search
engine.
An example: I perform a search in Tab-1 with search-engine-1. I select
from the search results and bring up a webpage. Now I want to perform
the
I vote against this. Search-box should NOT be tab specific.
If you open a new tab and then tap CTRL+K and start typing, it writes
over what was there. What is the problem with this? Why do you need the
search field blank? The behavior you guys are proposing has resulted in
a miserable experience
Like some others, I also object to keeping the legacy filter as the
default. Freetype doesn't call it legacy without reason: it is optimized
for one special rendering preference, full native hinting (IMO it's
doing badly even in that case), and is crap in all others. Moreover, if
the fonts do not
Like some others, I also object to keeping the legacy filter as the
default. Freetype doesn't call it legacy without reason: it is optimized
for one special rendering preference, full native hinting (IMO it's
doing badly even in that case), and is crap in all others. Moreover, if
the fonts do not
I have this problem now with 14.10
previously I had 14.04 installed and the screensaver was very
problematic - it would frequently not turn off the screen by itself, but
Ctrl-Shift-L always worked.
Now with 14.10 screensave never turns on and Ctrl-Shift-L never works.
Typing
Public bug reported:
MariaDB crashed during install. Did not successfully install.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mariadb-server-5.5 5.5.41-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
Affects me. Ubuntu 14.04. dig -x 192.168.1.101 takes a long time to
not come up with an answer. And that's because it's defined in
/etc/hosts.
lsof -i and tcpdump are two programs that can do do reverse-DNS lookups,
and ignoring /etc/hosts means they take way longer than they normally
would.
I just went from 14.04 LTS to 14.10 and now get the same error for any
PDF I open:
(evince:22053): Gtk-CRITICAL **: gtk_widget_show: assertion
'GTK_IS_WIDGET (widget)' failed
from Joe Chen's last message, are there some unmet GTK library
dependencies in 14.10?
--
You received this bug
Public bug reported:
Bug earlier resulted in several crashes
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-firmware 1.127.10
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Public bug reported:
Bug showed up on boot to desktop. Not sure of what reason as no message
was displayed other than to submit bug report
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic
Downgrading as of today (Jan 2015) doesn't seem really feasibile since
raring is gone. Can't find libcurl3-gnutls-7.29 anywhere. Isn't this
majorly awesome unix-y functionality that everybody uses? Surprised
it's broken.
Partial workaround is to use Vim's built-in FTP support. vim
I'm on Utopic, and have been having this problem for ages. Just to
confirm, I can't take the hold off ubuntu-drivers-common without
breaking everything, right?`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I answered my own question! It now works for me! Thanks, everyone!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use GUI after update
To manage notifications about
I disagree. Enabling ufw broke things, and disabling it should put them
back in working order. Also, ufw probably shouldn't break things when
enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
rt5572 perfectly works under rt2800USB module on unbuntu 14.04 x64
just assign vid pid to the driver and it wil work
echo vid pid /sys/bus/usb/drivers/rt2800usb/new_id
then plug usb stick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
xterm freezes sometimes. this never happened before trusty. under
trusty it's happening maybe two or three times a month, usually shortly
after i've booted and logged in and am launching things. i can startup
a new xterm which works fine, while the frozen one stays frozen,
no idea how it became nonexecutable. when executable it works. thank
you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400912
Title:
40_custom no longer included in grub.cfg
To manage
Public bug reported:
i even restored originals for etc/grub.d/40_custom and
etc/defaults/grub, but 40_custom still not being included in grub.cfg
anymore
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: grub-pc 2.02~beta2-9ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Public bug reported:
i use xterm daily, it freezes maybe a couple times per week. i
typically run tmux, so i can just open another xterm, reattach my tmux
session, and discard the frozen xterm. wasn't happening in releases
prior to trusty.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package:
Chris
My system is different now. I ditched Windows 7 and have a single boot
system. I am also using Ubuntu v14.04 and will soon go to v11.10. If I
recall the bug stopped with 11.10.
On Sun, 2014-11-16 at 21:04 +, Christopher M. Penalver wrote:
Greg Mack, thank you for reporting this bug
I also have the same bug with KDE 4.13.3 Plasma and kernel
3.13.0-39-generic. It is the KDE in Linux Mint 17 repositories which is
based on Ubuntu 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We are on ESXi, version 5.5, according to our hosting provider.
To run the test, I created a new, 40GB virtual disk. It's attached as
SCSI ID 1:3, on a VMware Paravirtual SCSI adapter. I set it up as a PV
and put ext4 on it the fast way, which is what I always do:
701 pvcreate /dev/sdd
Hi,
We just hit this bug on 3.13.0-39.66~precise1, running MongoDB 2.6.3.
We're running Precise, with the trusty HWE enabled. We're on VMware,
though from reading this bug report it doesn't matter.
Is there anything we can report to be helpful?
--
You received this bug notification because
The package now uses serial mumps. I will see if i can SRU this to older
ubuntu versions
** Changed in: coinor-ipopt (Ubuntu)
Assignee: (unassigned) = Greg (gregmainland)
** Changed in: coinor-ipopt (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification
** Changed in: coinor-ipopt (Ubuntu)
Assignee: (unassigned) = Greg (gregmainland)
** Changed in: coinor-ipopt (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: coinor-ipopt (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978196
Title:
pkg-config settings for ipopt should default to serial
** Changed in: coinor-ipopt (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167585
Title:
ipopt example does not run
To manage notifications
** Changed in: coinor-ipopt (Ubuntu)
Assignee: (unassigned) = Greg (gregmainland)
** Changed in: coinor-ipopt (Ubuntu)
Status: New = Fix Committed
** Changed in: coinor-ipopt (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you
** Description changed:
- I can only get the simple Cpp_example from IpOpt to run without crashing
- when I build IpOpt from source. When I use the package I get an MPI
- error. I think this is a packaging issue.
+ [IMPACT]
+ Any program using ipopt with default settings crashes.
+ This
** Changed in: coinor-ipopt (Ubuntu)
Assignee: (unassigned) = Greg (gregmainland)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388487
Title:
MATLAB crashes when IPOPT converges to machine
** Description changed:
[IMPACT]
Any program using ipopt with default settings crashes.
This includes upstream examples.
[REGRESSION POTENTIAL]
ABI/API incompatability? This doesn't seem like such a big deal
since this bug makes the package practically unusable.
[TEST CASE]
-
It sounds like this bug is unrelated to the coinor-ipopt package in
ubuntu, is that correct? Do you have the libcoinor-ipopt package
installed? You might try uninstalling it if you do. As MATLAB is
proprietary software this is difficult to debug.
Can you provide a stack trace of the crash?
**
Public bug reported:
Just trying to run a daily upgrade and it failed.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure key file permissions
To manage notifications about this bug go to:
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure key file permissions
To manage notifications about this bug go to:
Public bug reported:
openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-
updates/juno fails install (exit status 1)
full stack trace:
2014-10-27 20:40:42 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-27 20:40:43 INFO install Adding system user
Looks like it installed fine on a clean trusty lxc with cloud:trusty-
updates/juno -- so moving it this bug to the charm.
** Package changed: horizon (Ubuntu) = openstack-dashboard (Juju Charms
Collection)
** Summary changed:
- openstack-dashboard 2014.2-0ubuntu1~cloud0 from
Public bug reported:
openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-
updates/juno fails install (exit status 1)
full stack trace:
2014-10-27 20:40:42 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-27 20:40:43 INFO install Adding system user
Looks like it installed fine on a clean trusty lxc with cloud:trusty-
updates/juno -- so moving it this bug to the charm.
** Package changed: horizon (Ubuntu) = openstack-dashboard (Juju Charms
Collection)
** Summary changed:
- openstack-dashboard 2014.2-0ubuntu1~cloud0 from
I am currently having this exact problem with Linux Mint 17, Mate 64
bit, with LibreOffice Version: 4.2.6.3, Build ID: 420m0(Build:3). Very
irritating there is no fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
same here on 14.04, is there any good alternatives?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237404
Title:
Baobab shows 0 byte file size on smb mounts
To manage notifications about this bug
Retrieved 9/15 nightly Gnome and reinstalled.Then used synaptic and
retrieved unity 7. No problems now. I have gnome, cairo, lxde, and unity
desktop environments. All running perfectly!!!
On Sun, Oct 12, 2014 at 4:53 PM, Logan Rosen loganro...@gmail.com
wrote:
** Tags removed: bugpattern-needed
Blueprint changed by Greg Lutostanski:
Work items changed:
Work items:
- SRU version 1.5.4 of MAAS into Trusty: INPROGRESS
- MIR amtterm: TODO
- Add maas-samba as optional dep: TODO
+ SRU version 1.5.4 of MAAS into Trusty: DONE
+ Remove celery deps from 1.7 in Utopic: DONE
Testing for maas
This is fixed in the debian packages, which should eventually become
ubuntu packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947222
Title:
pkg-config file not installed
To manage
Public bug reported:
I enabled ufw to try it out, with the default settings. I disabled it,
but I still get errors when trying to use sendto() to localhost:
Errno::EPERM - Operation not permitted - sendto(2)
/var/log/syslog is full of:
Oct 5 14:42:14 host kernel: [9194390.533505]
As #8 and #18, same problem fixed with sudo apt-get install --reinstall
xserver-xorg-video-intel , which seems to have bumped the version up to
2:2.99.910 from 2.2.99.909-git .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ISO is valid, crashes again on reinstall
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376062
Title:
installer crashed
To manage
** Description changed:
- enlist the chassis with Glenn m700 cartridges of moonshot with 1.5.4
- MAAS in proposed using the command below sudo maas admin node-group
- probe-and-enlist-mscm 24b0fe1a-1e59-47d6-b446-d0711ee0c81c
- host=172.16.1.102 username=Administrator password=password
+ [Impact]
** Description changed:
+ Bug = the restart-popup-dialog that sometimes occurs after a system-
+ update should only run once. If the user declines to reboot from the
+ popup, then the power-cog should turn red until reboot occurs. Repeated
+ popups asking to reboot should not occur.
+
In
Let me first draw attention to the edit I made to my initial Bug
Description: I have expanded the Bug scope to the fact that the popup-
dialog repeats itself AND the power-cog icon does not turn red. After a
system updates, only one restart-popup should present (it serves
informational purposes
** Description changed:
- enlist the chassis with Glenn m700 cartridges of moonshot with 1.5.4
- MAAS in proposed using the command below sudo maas admin node-group
- probe-and-enlist-mscm 24b0fe1a-1e59-47d6-b446-d0711ee0c81c
- host=172.16.1.102 username=Administrator password=password
+ [Impact]
Public bug reported:
installer crashed towards end of install
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
I observe the same problem on 14.04 on HP EliteBook 840.
dmesg:
[0.00] Linux version 3.13.0-36-generic (buildd@toyol) (gcc version
4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014
(Ubuntu 3.13.0-36.63-generic 3.13.11.6)
[0.00] DMI: Hewlett-Packard HP
I'm am getting the JS ERROR posted above as well on 14.04, but a dbus
force-reload is not fixing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274433
Title:
64 bit gnome-maps fails to open in
** Description changed:
- No support for armhf/keystone architecture for ProLiant m800 Server
- Cartridges from HP.
+ [Impact]
+ * Add hardware enablement for armhf/keystone.
+
+ [Testcase]
+ * Enlist/Commission armhf/keystone hardware and make sure install proceeds
correctly.
+
+
** Description changed:
- No support for armhf/keystone architecture for ProLiant m800 Server
- Cartridges from HP.
+ [Impact]
+ * Add hardware enablement for armhf/keystone.
+
+ [Testcase]
+ * Enlist/Commission armhf/keystone hardware and make sure install proceeds
correctly.
+
+
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu)
Importance: Undecided = High
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu)
Importance: Undecided = High
unity8?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357785
Title:
apportcheckresume crashed with FileExistsError in main(): [Errno 17]
File exists:
Thanks for the reply, Matthew.
1) closing and opening the lid to cause sleep is unrelated to this
matter. Regardless of Suspend use, if a user intends to shutdown/restart
the computer, the power-cog is where the GUI user is going to go. If a
user never shuts down or restarts unless explicitly
Matthew Paul Thomas said:
The red icon dates from the era when the rightmost menu was a device menu,
trying to cover everything from attached printers to external displays to
software updates to screen locking, which was absurd. Nowadays everything to
do with software updates is integrated into
Thanks for that Curtis. Unfortunately there's no evidence that's the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205815
Title:
g_main_dispatch: assertion failed:
Sorry for the delay.
I can't reproduce the crash, but instead when trying to unmount the
drive it gets stuck at Searching /dev/sdb partitions. Even after
closing the Gparted window, I am left with three processes:
greg@lmh:~$ ps -A | grep gparted
15719 ?00:00:00 gparted-pkexec
15720
** Changed in: maas (Ubuntu Trusty)
Status: Fix Released = Fix Committed
--
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/1315154
Title:
[SRU] doesn't support booting ppc64el
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
--
You received this bug notification because you
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Low
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315154
Title:
[SRU] doesn't support booting ppc64el hardware
To
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
--
You received this bug notification because you
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Milestone: None = trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Low
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Changed in: maas (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Assignee: (unassigned) = Greg Lutostanski (lutostag)
** Changed in: maas (Ubuntu Trusty)
Milestone: None
** Summary changed:
- doesn't support booting ppc64el hardware
+ [SRU] doesn't support booting ppc64el hardware
--
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/1315154
Title:
[SRU]
** Description changed:
+ [Impact]
+ * Previously Django's aggressive connection closing policy would prevent
session-level locks from being maintained.
+
+ [Testcase]
+ * Run included tests
+
+ [Regression Potential]
+ * Minimal, potentially an issue as it deals with releasing a lock (it
** Description changed:
+ [Impact]
+ * When using new locking code, this is used to prevent an error on maas
server startup when asking for a lock when not in a transaction
+
+ [Testcase]
+ * Run included tests in test_start_up.py
+
+ [Regression Potential]
+ * Minimal
+
mod_wsgi
** Summary changed:
- Missing dependency on python-paramiko
+ [SRU] Missing dependency on python-paramiko
** Description changed:
- As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
- maas/131/console, maas package can't be installed on utopic due to a
- missing dependency
** Summary changed:
- ImportError: No module named pexpect when setting up maas-region-controller
+ [SRU] ImportError: No module named pexpect when setting up
maas-region-controller
** Description changed:
+ [Impact]
+ * Install required deps for maas-provisioningserver (move from
** Summary changed:
- doesn't support booting ppc64el hardware
+ [SRU] doesn't support booting ppc64el hardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315154
Title:
[SRU] doesn't support
** Description changed:
+ [Impact]
+ * Previously Django's aggressive connection closing policy would prevent
session-level locks from being maintained.
+
+ [Testcase]
+ * Run included tests
+
+ [Regression Potential]
+ * Minimal, potentially an issue as it deals with releasing a lock (it
** Description changed:
+ [Impact]
+ * When using new locking code, this is used to prevent an error on maas
server startup when asking for a lock when not in a transaction
+
+ [Testcase]
+ * Run included tests in test_start_up.py
+
+ [Regression Potential]
+ * Minimal
+
mod_wsgi
** Summary changed:
- Missing dependency on python-paramiko
+ [SRU] Missing dependency on python-paramiko
** Description changed:
- As seen here: http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/utopic-adt-
- maas/131/console, maas package can't be installed on utopic due to a
- missing dependency
** Summary changed:
- ImportError: No module named pexpect when setting up maas-region-controller
+ [SRU] ImportError: No module named pexpect when setting up
maas-region-controller
** Description changed:
+ [Impact]
+ * Install required deps for maas-provisioningserver (move from
** Description changed:
+
+ SRU for secondary fix (branch lp:~julian-edwards/maas/nonce-fix-bug-1190986)
+ [Impact]
+ * Minimize possibility of hitting a nonce collision by using a longer nonce
(uuid4) in both python-maas-client and commissioning scripts.
+
+ [Testcase]
+ * Do some api calls
** Description changed:
- It looks like maas needs support added for utopic. Could you also
- consider implementing this so that it is configurable in a config file?
- It would be much better than needing a hard-coded update each release.
+ [Impact]
+ * Remove no longer supported distro
401 - 500 of 6016 matches
Mail list logo
