From James's duplicate bug:
In our MAAS based openstack deployment, we provide MTU via DHCP to all
servers to enable jumbo frames.
This works fine until juju creates the bridge devices for LXC or KVM
containers, at which point we reliably lose the MTU 9000 setting on the
bridge, resulting in all
** Changed in: juju-core
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
To
The stilson machines that run the tests have 9.8G RAM. They always have.
** Changed in: gccgo-go (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/1393825
** Changed in: juju-release-tools
Status: Triaged = Invalid
** Changed in: gccgo-go (Ubuntu Vivid)
Status: Confirmed = Fix Released
** Changed in: gccgo-5 (Ubuntu Vivid)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of
** Changed in: juju-release-tools
Status: Triaged = Invalid
** Changed in: gccgo-go (Ubuntu Vivid)
Status: Confirmed = Fix Released
** Changed in: gccgo-5 (Ubuntu Vivid)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of
There has been a lot confusion about this bug. As the reporter, I am
happy to say vivid packaging (or cloud/builder images) were fixed last
week. Without any changes to juju packaging. Launchpad and lxc can
again built vivid ppc64el packages without explicitly setting the GOARCH
to match the dpkg
The last 2 Lp builds of juju packages succeeded, as does my own builds.
I think this issue resolved itself since I did not change packaging
rules. I will do a little more investigation, but hope to close this bug
in a few hours.
--
You received this bug notification because you are a member of
** Tags added: maas-provider network
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: openal-soft (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/1416042
Title:
crashing when building with SSE
To manage notifications
We captured a snippet of the private build log and we can see the issue
is the same as the report. The first call to access bin/juju fails
because it is not there, it is in $GOPATH/bin/linux__ppc64le. VIvid's
gccgo-go thinks it is cross-compiling.
mkdir -p
** Description changed:
The vivid ppc64el builds are failing. The last success was on
2015-01.20. their first failure was on 2015-01-23.
We suspect that golang-go sets the wrong GOARCH in vivid.
We cannot see the build logs because Lp is a punk. The builds were in the
~juju-package
There are non-trivial changes between precise's (1.14) and trusty's
(1.15) versions of libopenal-soft.
If you don't need it, no worries. If you do need it, just re-install it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Going to close this with fixed, as this is old, no one is responding and
when I tested, I couldn't reproduce it.
** Changed in: wildmidi (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What version of gstreamer? You'll likely have to install the ugly
package to get the plugin.
You can test directly by using the wildmidi player to play back your
midi. If it works for you, then the fault exists with Gstreamer or
totem/rythembox.
--
You received this bug notification because
) = Bret Curtis (psi29a)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1416042
Title:
crashing when building with SSE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
: High
Assignee: Curtis Hovey (sinzui)
Status: Triaged
** Affects: gccgo-go (Ubuntu)
Importance: Undecided
Status: New
** Tags: packaging ppc64el vivid
** Changed in: juju-release-tools
Assignee: (unassigned) = Curtis Hovey (sinzui)
** Also affects: gccgo-go (Ubuntu
: High
Assignee: Curtis Hovey (sinzui)
Status: Triaged
** Affects: gccgo-go (Ubuntu)
Importance: Undecided
Status: New
** Tags: packaging ppc64el vivid
** Changed in: juju-release-tools
Assignee: (unassigned) = Curtis Hovey (sinzui)
** Also affects: gccgo-go (Ubuntu
Affects me as well: Ubuntu 14.04 and Galaxy S3. Toggling USB debugging
off and back on again had no effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314556
Title:
Unable to mount Android MTP
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
To
** Changed in: juju-core
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/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications
** Changed in: juju-core
Status: Incomplete = 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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
** Changed in: juju-core
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1316579
Title:
--upload-tools doesn't work with bootstrap on
** Changed in: juju-core
Milestone: 1.23 = None
** Changed in: juju-core
Importance: High = Medium
--
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/1393444
Title:
machine
** Changed in: juju-core
Milestone: 1.23 = None
** Changed in: juju-core
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393444
Title:
machine unit connects to
** Changed in: juju-core
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/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
We have frozen juju 1.22. We expect it to ship with vivid. This feature
will need to be back-ported. How does Ubuntu feel about adding a feature
to 1.22.1? If this is bad, then we will wait for 1.23 to be backported
to w, v and t.
** Changed in: juju-core
Milestone: None = 1.23
** Changed
We have frozen juju 1.22. We expect it to ship with vivid. This feature
will need to be back-ported. How does Ubuntu feel about adding a feature
to 1.22.1? If this is bad, then we will wait for 1.23 to be backported
to w, v and t.
** Changed in: juju-core
Milestone: None = 1.23
** Changed
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1402005
Title:
agent-state-info: 'error executing lxc-start: command get_cgroup
failed to
** Changed in: juju-core
Status: Triaged = Invalid
--
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/1402005
Title:
agent-state-info: 'error executing lxc-start: command get_cgroup
** Changed in: juju-core
Milestone: 1.22 = None
--
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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine
** Changed in: juju-core
Milestone: 1.22 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
maas
To
This is unsetting. That is the error I saw, but with a different juju
and series. 1.20.13 on MY trusty saw that error. Older jujus or newer
quick-starts worked. The juju-gui team had not seen the issue before,
the concluded my setup had tainted the test. When we retested with a
pristine trusty, it
This is unsetting. That is the error I saw, but with a different juju
and series. 1.20.13 on MY trusty saw that error. Older jujus or newer
quick-starts worked. The juju-gui team had not seen the issue before,
the concluded my setup had tainted the test. When we retested with a
pristine trusty, it
Ubuntu has old packages
https://launchpad.net/~sinzui/+archive/ubuntu/ppa?field.series_filter=trusty
1.1.0+661-0~gdp~ubuntu13.10.1 was rebuilt for trusty and it works well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The restricted-network test fails because of the upstream dep. We are
changing the test to use trusty (as series is not relevant).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
The restricted-network test fails because of the upstream dep. We are
changing the test to use trusty (as series is not relevant).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407699
Title:
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1407699
Title:
Precise services cannot be deployed
To manage
** Changed in: juju-core
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/1407699
Title:
Precise services cannot be deployed
To manage notifications about
I tried raising this issue on bugzilla.gnome.org, but their opinion is that it
is not a GNOME Shell problem (Comment #7) since the indicator-multiload graphs
are displayed in a panel:
https://bugzilla.gnome.org/show_bug.cgi?id=741887
Obviously, something changed somewhere between Ubuntu 12.04
** Changed in: juju-core/1.21
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Tags added: lxc network
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: juju-core/1.21
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/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Tags added: lxc network
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1402763
I think my test of juju-quickstart + juju-core failed because my env is
dirty. I get the same errors on trusty with the packages in release and
updates. I will retest with a clean trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
I think my test of juju-quickstart + juju-core failed because my env is
dirty. I get the same errors on trusty with the packages in release and
updates. I will retest with a clean trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
juju-quickstart 1.3.1 + juju-core 1.20.11 in trusty cannot connect to
the bootstraped start-server to deploy services.
18:40:09 WARNING app@connect:300 Retrying: unable to connect to the
Juju API server on wss://165.225.151.107:17070: [Errno 1] _ssl.c:510:
error:14090086:SSL
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
juju-quickstart 1.3.1 + juju-core 1.20.11 in trusty cannot connect to
the bootstraped start-server to deploy services.
18:40:09 WARNING app@connect:300 Retrying: unable to connect to the
Juju API server on wss://165.225.151.107:17070: [Errno 1] _ssl.c:510:
error:14090086:SSL
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
lxc*1.0.3 looks odd. That is one version I don't expect to see.
trusty has 1.0.6 which is what I think the host is and should be using.
a precise host has 1.0.4
found in the cloud tools archive
http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/l/lxc/
juju stable ppa provides
The host machine is trusty and was missing updated. We have updated the
lxc and other packages. We will watch the processes to see if the issue
is resolved or still exists.
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags
** Changed in: scratch (Ubuntu)
Assignee: (unassigned) = Curtis (curtiscasha)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025013
Title:
Resize scratch window, it doesn't update, goes black
lxc*1.0.3 looks odd. That is one version I don't expect to see.
trusty has 1.0.6 which is what I think the host is and should be using.
a precise host has 1.0.4
found in the cloud tools archive
http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/l/lxc/
juju stable ppa provides
The host machine is trusty and was missing updated. We have updated the
lxc and other packages. We will watch the processes to see if the issue
is resolved or still exists.
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags
** Changed in: juju-core
Milestone: 1.21 = 1.22
--
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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine
** Changed in: juju-core
Milestone: 1.21 = 1.22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
maas
To
I tried applying the patch in comment 22 to my 14.04 installation
(3.13.0-39-generic, upgraded from 12.04) and rebooting, but it didn't
solve the problem with my Logitec webcam microphone. I still get the
same error.
ubuntu-drivers-common 1:0.2.91.7 is the currently installed version.
Are they
Forgot to mention I am using Gnome3 shell, not Unity or KDE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device management
Juju QA certifies that the trusty clients are suitable for local
development and production cloud deploys.
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land
Juju QA certifies that the trusty clients are suitable for local
development and production cloud deploys.
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
Vivid testing is complete. It is suitable for local development and for
deploying to clouds.
Trusty testing is blocked by the missing juju-local package for 14.14.
The vivid local package can be forced to install, but it depends on
juju-core = 1.20.11-0ubuntu1, but the trusty backport is
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
Vivid testing is complete. It is suitable for local development and for
deploying to clouds.
Trusty testing is blocked by the missing juju-local package for 14.14.
The vivid local package can be forced to install, but it depends on
juju-core = 1.20.11-0ubuntu1, but the trusty backport is
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: upgrade-juju
** Tags added: lxc
** Changed in: juju-core
Milestone: None = 1.22
--
You
The juju-local package does not appear to have been built and published.
the i386 juju-core package was built but is not listed as published.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/1386144
Public bug reported:
what else u wanna know? it dont work
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.17.0
ProcVersionSignature: Ubuntu 3.12.0-2.5-generic 3.12.0
Uname: Linux 3.12.0-2-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.6-0ubuntu1
Architecture: amd64
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: upgrade-juju
** Tags added: lxc
** Changed in: juju-core
Milestone: None = 1.22
--
You
The juju-local package does not appear to have been built and published.
the i386 juju-core package was built but is not listed as published.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
** Changed in: ubuntuone-servers
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848529
Title:
Choose between binary prefixes and SI
** Changed in: create-project
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781350
Title:
Name: header is missing in several swatch
*** This bug is a duplicate of bug 848529 ***
https://bugs.launchpad.net/bugs/848529
** Changed in: ubuntuone-servers
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntuone-servers
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736786
Title:
Ubuntu One notes editor doesn't apply
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications
** Changed in: juju-core
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/1078213
Title:
logs are not logrotated
To manage notifications about this bug go
** Tags added: cts-cloud-review
** Tags added: add-unit
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: placement
** Tags added: network
** Changed in: juju-core
Milestone: None = 1.22
** Changed in:
** Changed in: distro-info (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390133
Title:
Information about Vivid is not available in Precise
To manage
** Tags added: cts-cloud-review
** Tags added: add-unit
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: placement
** Tags added: network
** Changed in: juju-core
Milestone: None = 1.22
** Changed in:
Thank you. Our precise machine now sees the updated package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390133
Title:
Information about Vivid is not available in Precise
To manage
** Changed in: juju-core
Milestone: 1.21-alpha3 = 1.21-beta1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications about
** Tags removed: cts local
** Tags added: cts-cloud-review local-provider
--
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/1290920
Title:
non-default lxc-dir breaks local provider
** Changed in: juju-core
Milestone: 1.21-alpha3 = 1.21-beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications about this bug go to:
** Tags removed: cts local
** Tags added: cts-cloud-review local-provider
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290920
Title:
non-default lxc-dir breaks local provider
To manage
Public bug reported:
crashed on install
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture:
Thank you Phillip for the clarification about only the fix being back-
ported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376051
Title:
gpartedbin crashed with SIGABRT in g_assertion_message()
Thank you Phillip for following up on these problems and back-porting
the appropriate patches. :-)
If I understand your post correctly, the second bug was introduced in
0.19. Was this second bug fixed in 0.19.1 by Prevent cross thread
write after free in _OnReadable() (#731752) ?
I guess what
** Changed in: juju-core
Importance: High = Medium
** Changed in: juju-core
Milestone: next-stable = None
--
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/1318378
Title:
** Changed in: juju-core
Importance: High = Medium
** Changed in: juju-core
Milestone: next-stable = None
--
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/1347322
Title:
** Changed in: juju-core
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1306315
Title:
juju-mongodb process hangs around after package removal
To
?
Curtis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376051
Title:
gpartedbin crashed with SIGABRT in g_assertion_message()
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Changed in: juju-core
Importance: High = Medium
** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318378
Title:
rsyslog starts
** Changed in: juju-core
Importance: High = Medium
** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a
** Changed in: juju-core
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306315
Title:
juju-mongodb process hangs around after package removal
To manage notifications
GParted 0.18.0 contains some bugs known to cause crashes.
See:
Bug 729139 - Refactor OperationDetail to address random crash behavior
https://bugzilla.gnome.org/show_bug.cgi?id=729139
Bug 731752 - Write after free cross thread race in PipeCapture::_OnReadable()
causes crash
GParted 0.19.0 contains a bug known to cause crashes.
See:
Bug 731752 - Write after free cross thread race in PipeCapture::_OnReadable()
causes crash
https://bugzilla.gnome.org/show_bug.cgi?id=731752
Can you retry using GParted 0.20.0?
The easiest way might be to boot from media containing
** Changed in: juju-core
Milestone: 1.21-alpha2 = 1.21-alpha3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications about
** Changed in: juju-core
Milestone: 1.21-alpha2 = 1.21-alpha3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications about this bug go to:
801 - 900 of 5893 matches
Mail list logo
