Here's the output when I re-run wallch from a terminal. The Glib
messages appear when I click Browse:
Error: The message '--focus' could not be sent to Wallch.
Assuming that the previous Wallch instance crashed and starting a new one
now. Sorry for this :)
libpng warning: iCCP:
Public bug reported:
When I start up Wallch (never having run it before on this system), I
click the "Browse" button for the "Pictures location." Nothing happens,
no dialogue appears, and the UI becomes unresponsive.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: wallch 4.0-0ubuntu4
Hello? Any corrections for that revisions range you wanted me to
bisect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications
Public bug reported:
Automatically reported crash.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331-updates-uvm 340.76-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic i686
ApportVersion: 2.17.2-0ubuntu1.1
Architecture:
Public bug reported:
Laptop insisted on upgrade from 14.10 to 15.04 on the day before travel.
Took hours, so I let it upgrade overnight. Partway through it got stuck
on some pointless press-OK-to-acknowledge dialog, so it wasn't done the
following morning; there was no way to stop the upgrade
This last weird effect was transient; it went away after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications about this
It just got a bit weirder.
I've got my custom xrandr-defined 2560×1440 resolution going. But for
purposes like window placement, resizing windows, and maximising
windows, the UI seems to think it's 1920×1080 or thereabouts.
So if I open a whole bunch of editor windows from the shell, they all
This is getting awkward. The upper-bound version you wanted me to
bisect is also missing from the Ubuntu/upstream version mapping. So
even if I want to bisect upstream versions I still have the same
problem. Are you sure you gave me the correct versions for bisection?
Maybe you meant
Thanks. Could you also update that section? It says that it applies in
two situations, but it never actually lists those two situations. I
*think* (but without already knowing of course I can't be sure) that
it's meant to refer to a list of three headings, “BISECTING: A MERGE
BASE MUST BE
Thanks for following up. I read most of that document, but it's
difficult in places. My understanding is that what you're asking me to
do is what's described under “Commit bisecting Ubuntu kernel versions,”
correct? That's the only part of the main page (excluding the FAQ
below) that seems to
If you don't have time to read what I wrote, or if something I wrote is
not clear, just say so and I will understand. Let's not get caught in
the endless Confirmed/Incomplete circle.
I'll summarise what I said before, to make it easier to digest:
You asked me to bisect between 3.13.0.18.38 and
Read back and it will become clear.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer
Once again: with the given instructions I can't bisect kernel commits
any further. Is there another way to obtain the kernel source versions
we need?
Marking as Confirmed again until then, to avoid this bug timing out.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You
3.13.0-19.40 also works OK! So it broke sometime after that.
I'm now trying to find 3.13.0-20.24 in one of the kernel branches from
before Vivid. It's not in the Trusty branch. I can't get the Quantal,
Raring, or Saucy ones, presumably because those releases are no longer
supported.
Using the ubuntu-vivid kernel branch, 3.13.0-18.38 works OK.
That branch has no tag Ubuntu-3.13.0.20.24 or Ubuntu-3.13.0-20.24. The
closest tags I see are Ubuntu-3.13.0-19.40 and Ubuntu-3.13.0-20.41.
I'll try 3.13.0-19.40 next.
--
You received this bug notification because you are a member of
The Precise kernel repository finished downloading, but it doesn't have
3.13.0-20.24. It has 3.13.0-19.39 and 3.13.0-20.41, nothing inbetween.
Pinning my hopes on the Utopic branch...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nope, the Utopic kernel branch only has 3.13.0-19.40 and 3.13.0-20.41,
nothing inbetween.
So, all I know is up to and including 3.13.0-19.40 it still works OK.
The problem must have been introduced later than that.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You
Oh, one other thing: with the older kernels I can play AssaultCube
again! I couldn't really do that with the current Vivid kernels because
the frame rate was too low. Reported frame rate would be around 60 fps,
but it looks more like 10 fps. With these old kernels it plays
smoothly.
--
You
Tried 4.1-rc8 as well for good measure. Still no improvement. Highest
resolution offered in the System Settings is 1920×1200.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen
No Tried 4.1-rc7. No change.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To
Marking this bug as Confirmed to avoid timeout. It was marked
Incomplete pending testing against Saucy, but as of a few months ago the
results are shown above.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
Saw a bunch of at-spi2 errors in .xsession-errors. Reinstalled at-
spi2-core, and those errors went away. Still no desktop. Deleting
.config/dconf/user did the trick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After another reboot this effect seems to have gone away. So I still
don't have my native resolution available by default, but at least I can
get it back by defining it with xrandr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hurray, the problem just got a little worse!
After the upgrade to kernel 3.19.0-14.14, when I define my monitor's
native resolution using xrandr, I get the right *resolution* but still
not the right number of *pixels*. So I'm getting (as far as I can see)
one logical pixel per physical pixel on
Correction: that last upgrade was *from* 3.19.0-14.14, not *to* it. It
was the upgrade to 3.19.0-15.15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer
So to be clear: my desktop is still utterly broken, but the one on an
installer disc for the same version is not. Hopefully there is a simple
configuration problem. I haven't done anything very special, I thought.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After some searching, I found a comment suggesting that resetting my ATI
graphics driver using aticonfig --initial might help. I did that, and
now I get slightly further.
Now when I log in I get the basic file management functionality on the
desktop: icons and a context menu. But no Unity
A piece of good news: I did get a working desktop when booting from the
14.10 installer, for the same architecture.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437765
Title:
No desktop after
While the system is in this state, ps does show a compiz process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437765
Title:
No desktop after upgrade to 14.10
To manage notifications about this
Public bug reported:
After upgrading my desktop machine from 14.04 to 14.10, I no longer have
a desktop. The login screen works, but after logging in, I get just the
backdrop image and a mouse pointer. Nothing else.
The pointer responds to mouse movements, and I can switch to a text
console
Well, I did some bisecting but the results are disappointing. Actually
I ended up trisecting. On Saucy, kernel...
3.11.0-12 was OK. Recognised my full native resolution and enabled it
by default. Wonderful.
3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted
in some
Public bug reported:
Trying to install this on a 15.04 system, together with the generic
kernel image, in order to see if it makes a regression since 14.04 go
away (bug 1300557).
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fwts-efi-runtime-dkms 15.03.00-0ubuntu1
Trying 13.11.0-17. There was a problem while installing linux-headers
though... fwts-efi-runtime-dkmis 15.03.00-0ubuntu1: fwts-efi-runtime-
dkms kernel module failed to build. Somewhere along the way it said:
run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-17-generic
Okay, I got a seemingly successful install of the last Saucy kernel.
But it's not working very well: I get a super-low-res login screen, and
the system doesn't respond to keyboard or mouse. (It does notice the
power button, so it's not frozen). This happens both with the default
boot on that
I could temporarily swap out the hard drive and install Saucy on the
spare. More after the weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
The latest upstream version I found there was v4.0-rc4-vivid. It boots,
but it doesn't fix the problem.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The version that was installed on March 31 was 3.13.0.20.24. The
version I uninstalled right after that was 3.13.0.18.38.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen
According to the dpkg.log for that date, quite a lot: libc-bin for
amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6
etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0,
libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk,
Something happened to this bug's conversation: the message asking me to
upgrade the BIOS has been removed/hidden.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no
I first upgraded to 14.10; that didn't change anything. Trying 15.04
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
To manage notifications
No change in 15.04. I can add the resolution with xrandr, and after
that I can use it. But after reboot, I have to do it again.
The upgrade got stuck with a black screen and no networking, but I
eventually got out of it with the apt-get dist-upgrade dance from the
console. I hope that hasn't
I'm trying the BIOS upgrade as per those instructions. The only
applicable option was the flashrom one, which seems to have hosed my
BIOS. It's still on now, but I won't be able to boot it again. Kindly
mark this bug New again to give me time to recover and retry!
--
You received this bug
Okay, I got out of that situation with the help of the flashrom people.
My BIOS is now updated.
It helped a bit in that I can now define and add my resolution again
using xrandr. It won't stay added though: I need to define and add it
every time I boot. Otherwise, the resolution is not in the
** Changed in: maas
Status: In Progress = Fix Committed
** Changed in: maas (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: In Progress = Fix Committed
** Changed in: maas (Ubuntu)
Status: In Progress = 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/1373261
Title:
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = In Progress
** Branch linked: lp:~jtv/maas/bug-1373261
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas
Status: Triaged = In Progress
** Branch linked: lp:~jtv/maas/bug-1373261
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
- Reconfiguring between an IPv4-based and an IPv6-based MAAS_URL broke the
- ‘generator’ setting in my pserv.yaml: it ended up being the full IPv4
- netloc, with most of the IPv6 netloc tacked onto it.
+ Reconfiguring when the existing MAAS_URL used an IPv6 host address
** Description changed:
- Reconfiguring between an IPv4-based and an IPv6-based MAAS_URL broke the
- ‘generator’ setting in my pserv.yaml: it ended up being the full IPv4
- netloc, with most of the IPv6 netloc tacked onto it.
+ Reconfiguring when the existing MAAS_URL used an IPv6 host address
now contains...
generator: http://10.9.9.1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/
Note how the first part of the netloc, up to the first colon, is
replaced with the new address — but the rest of the netloc is still
there.
** Changed in: maas
Assignee: Jeroen T. Vermeulen (jtv
now contains...
generator: http://10.9.9.1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/
Note how the first part of the netloc, up to the first colon, is
replaced with the new address — but the rest of the netloc is still
there.
** Changed in: maas
Assignee: Jeroen T. Vermeulen (jtv
There doesn't seem to be any need to install with the C locale;
en_US.UTF-8 works just as well. As does installing the language pack(s)
to match the session's locale settings. The real problem is that we
have no hook for doing either before apt installs our dependencies: it
installs the
I agree: this is a clear-cut case for the request-an-address API, but we
still lack a request-a-hostname API.
Out of curiosity, how did the existing setup(s) obtain these generated
hostnames in the first place? To my knowledge they were neither exposed
nor documented. MAAS never had much
Ah, I see that using the IP address is not an option in this case. So
we'll have to add a way to manage DNS entries.
--
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/1382190
Title:
Ah, I see that using the IP address is not an option in this case. So
we'll have to add a way to manage DNS entries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382190
Title:
LXCs assigned IPs
I agree: this is a clear-cut case for the request-an-address API, but we
still lack a request-a-hostname API.
Out of curiosity, how did the existing setup(s) obtain these generated
hostnames in the first place? To my knowledge they were neither exposed
nor documented. MAAS never had much
MAAS trunk no longer includes Avahi, so closing this bug there.
** Changed in: maas
Status: Triaged = 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/1251257
Title:
[SRU] avahi
Public bug reported:
When I “make package” (with trunk r3227 and packaging r317) I get this
error:
«
patching file contrib/maas_local_settings.py
Hunk #2 FAILED at 81.
1 out of 2 hunks FAILED
dpkg-source: info: fuzz is not allowed when applying patches
dpkg-source: info: if patch
Public bug reported:
When I “make package” (with trunk r3227 and packaging r317) I get this
error:
«
patching file contrib/maas_local_settings.py
Hunk #2 FAILED at 81.
1 out of 2 hunks FAILED
dpkg-source: info: fuzz is not allowed when applying patches
dpkg-source: info: if patch
Could this be bug 1186662? The main packaging branch has a workaround
for that which is worth a try.
It's a matter of adding this line to /etc/apparmor.d/dhcpd.d/maas:
capability dac_override,
...and then reloading the apparmor config.
--
You received this bug notification because you
Could this be bug 1186662? The main packaging branch has a workaround
for that which is worth a try.
It's a matter of adding this line to /etc/apparmor.d/dhcpd.d/maas:
capability dac_override,
...and then reloading the apparmor config.
--
You received this bug notification because you
I'm sure after all this time the problem no longer exists. Nor does the
system it happened on.
** Changed in: libburn (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, my hypothesis doesn't look correct. We don't see anything that
would make prepare() jump into the reactor thread.
--
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/1308069
Title:
New hypothesis: the code in DatabaseLock opens, and closes, a cursor for
each locking/unlocking command. Do we actually know that these cursors
will be in the same database session? If the command failed, do we know
that we would see an error?
--
You received this bug notification because you
No, my hypothesis doesn't look correct. We don't see anything that
would make prepare() jump into the reactor thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308069
Title:
New hypothesis: the code in DatabaseLock opens, and closes, a cursor for
each locking/unlocking command. Do we actually know that these cursors
will be in the same database session? If the command failed, do we know
that we would see an error?
--
You received this bug notification because you
It happened again. I suspect that it may be a matter of ordering of
decorators: RegionAdvertisingService.prepare is decorated as
@synchronous, and *then* as taking two locks.
Given decorators' wrapping behaviour, which reverses the order of
entrance, I understand that to mean: grab these two
It happened again. I suspect that it may be a matter of ordering of
decorators: RegionAdvertisingService.prepare is decorated as
@synchronous, and *then* as taking two locks.
Given decorators' wrapping behaviour, which reverses the order of
entrance, I understand that to mean: grab these two
Public bug reported:
Breakage during installation, on a fresh (near-pristine) amd64 14.04
system.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libclang1-3.5 1:3.5~svn201651-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
** Branch linked: lp:~jtv/maas/revert-bug-1311433
--
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/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
** Branch linked: lp:~jtv/maas/1.5-revert-bug-1311433
--
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/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
** Branch linked: lp:~jtv/maas/revert-bug-1311433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
attribute '__module__'
** Branch linked: lp:~jtv/maas/1.5-revert-bug-1311433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
attribute
** Description changed:
+ [Test Case]
+ No test case; the code that's being patched is only a test and does not
actually appear in the package.
+
+
+ [Description of the problem]
+
This happened when trying to land a documentation-only branch:
** Description changed:
+ [Test Case]
+ No test case; the code that's being patched is only a test and does not
actually appear in the package.
+
+
+ [Description of the problem]
+
This happened when trying to land a documentation-only branch:
Public bug reported:
I just upgraded a desktop system from 13.10 to 14.04, and to my horror
found that the monitor's native resolution was no longer supported: the
best setting offered was 1024×768 or somesuch.
Turns out the upgrade deleted xorg.conf. There were two backups: one
with the date
Also, I don't know if these are related, but window menus now appear not
only at the top of the screen or in the window's title bar (depending on
the new configuration setting in 14.04), but also in the classic pre-
Unity location: right below the window's title bar.
--
You received this bug
It's beginning to look like an nvidia driver problem. I tried switching
to Noveau; that left me with a resolution of 640×480, with no other
options. (In case you're wondering: it looks great but isn't very
practical). Switching back to the proprietary driver deleted my
xorg.conf again. After a
Upstream bug seems to be https://code.djangoproject.com/ticket/22486
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError:
** Branch linked: lp:~jtv/maas/1.5-use-main-archive-for-intel-arches
--
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/1310082
Title:
d-i with precise+hwe-s stops at Architecture not
** Branch linked: lp:~jtv/maas/1.5-use-main-archive-for-intel-arches
--
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/1310076
Title:
lost connectivity to a node when using
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas/1.5
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https
Upstream bug seems to be https://code.djangoproject.com/ticket/22486
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
** Branch linked: lp:~jtv/maas/1.5-use-main-archive-for-intel-arches
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310082
Title:
d-i with precise+hwe-s stops at Architecture not supported
To
** Branch linked: lp:~jtv/maas/1.5-use-main-archive-for-intel-arches
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using fastpath-installer with
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas/1.5
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I am attaching a fix for the part of the problem that's in
maas/preseeds/curtin_userdata, in the maas source tree. This won't be
enough to fix the whole problem, so I am not marking the branch as
“fixing” this bug.
** Branch linked: lp:~jtv/maas/use-main-archive-for-intel-arches
--
You
** Branch linked: lp:~jtv/maas/use-main-archive-for-intel-arches
--
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/1310082
Title:
d-i with precise+hwe-s stops at Architecture not
I am attaching a fix for the part of the problem that's in
maas/preseeds/curtin_userdata, in the maas source tree. This won't be
enough to fix the whole problem, so I am not marking the branch as
“fixing” this bug.
** Branch linked: lp:~jtv/maas/use-main-archive-for-intel-arches
--
You
** Branch linked: lp:~jtv/maas/use-main-archive-for-intel-arches
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310082
Title:
d-i with precise+hwe-s stops at Architecture not supported
To manage
The latest build in ppa:maas-maintainers/dailybuilds should have the
fix. Could you try again, but with that package?
--
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/1302772
Title:
** Changed in: maas
Status: In Progress = 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/1302772
Title:
update of maas-cluster-controller on trusty dumps
The latest build in ppa:maas-maintainers/dailybuilds should have the
fix. Could you try again, but with that package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302772
Title:
update of
** Changed in: maas
Status: In Progress = 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/1302772
Title:
update of maas-cluster-controller on trusty dumps traceback and
crashes
** Changed in: maas/1.5
Milestone: None = 14.04
** Changed in: maas
Milestone: None = 14.10
--
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/1302772
Title:
update of
** Changed in: maas/1.5
Milestone: None = 14.04
** Changed in: maas
Milestone: None = 14.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302772
Title:
update of maas-cluster-controller
That sounds as if it's probably just bug 1300548, which is already
fixed. Definitely not the same thing that this bug is about.
** Changed in: maas
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
That sounds as if it's probably just bug 1300548, which is already
fixed. Definitely not the same thing that this bug is about.
** Changed in: maas
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 541 matches
Mail list logo
