** Changed in: juju-core
Importance: Low = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't
** Changed in: juju-core
Importance: Low = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307445
Title:
openstack: instances with multiple nics on the same network don't have
Is there anything blocking 1.22.6 going into wily and trusty. I believe
I provided two SPB that I believe are good.
--
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/1469744
Title:
Is there anything blocking 1.22.6 going into wily and trusty. I believe
I provided two SPB that I believe are good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469744
Title:
[needs-packaging]
Public bug reported:
This is a meta bug. mongo 2.6 can drop or corrupt connections.
This bug will be fixed when either juju find a way to restore the
connection, or a fixed mongodb is distributed and available to precise
users and above.
** Affects: juju-core
Importance: Medium
Public bug reported:
This is a meta bug. mongo 2.6 can drop or corrupt connections.
This bug will be fixed when either juju find a way to restore the
connection, or a fixed mongodb is distributed and available to precise
users and above.
** Affects: juju-core
Importance: Medium
I prepared a source package for juju 1.22.6 in wily
lp:~sinzui/ubuntu/wily/juju-core/wily-1.22.6
Like the trusty package, I used the 1.22.5 as the base. The diff contains the
expected copyright correct that we reported was an issue when reviewing 1.22.5
I prepared a source package for juju 1.22.6 in wily
lp:~sinzui/ubuntu/wily/juju-core/wily-1.22.6
Like the trusty package, I used the 1.22.5 as the base. The diff contains the
expected copyright correct that we reported was an issue when reviewing 1.22.5
I am preparing a branch for 1.22.6 for wily. the local test did not pass
and I am looking into why lxc-br0 is missing after the adt image is
rebooted with upstart installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am preparing a branch for 1.22.6 for wily. the local test did not pass
and I am looking into why lxc-br0 is missing after the adt image is
rebooted with upstart installed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
Public bug reported:
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Stable Fix]
[sinzui] Prepare source
Hi Robie.
I opened a new bug to track the specific request of placing 1.22.6 into
trusty. I have prepared a new source package branch using the trusty
1.22.5 branch I proposed for bug 1462001.
We can see src/github.com/juju/txn changed; review the change for
copyright issues. The only change is
This is the diff from 1.22.5 to 1.22.6
http://pastebin.ubuntu.com/11793455/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469744
Title:
[needs-packaging] 1.22.6 is not packaged in trusty
To
This is the diff from 1.22.5 to 1.22.6
http://pastebin.ubuntu.com/11793455/
--
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/1469744
Title:
[needs-packaging] 1.22.6 is not packaged
Hi Robie.
I opened a new bug to track the specific request of placing 1.22.6 into
trusty. I have prepared a new source package branch using the trusty
1.22.5 branch I proposed for bug 1462001.
We can see src/github.com/juju/txn changed; review the change for
copyright issues. The only change is
Public bug reported:
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Stable Fix]
[sinzui] Prepare source
** Description changed:
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Stable Fix]
-
** Description changed:
We're now in a position to have 1.22.6 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Stable Fix]
-
I tested 1.22.5 from wily-proposed. It is suitable to create and
maintain cloud deployments. It is compatible with both juju-quickstart
and juju-deployer. Note, as with Vivid, 1.22.x is not fit for local
charm development and testing because it is not systemd aware. We expect
to propose juju 1.24
I tested 1.22.5 from wily-proposed. It is suitable to create and
maintain cloud deployments. It is compatible with both juju-quickstart
and juju-deployer. Note, as with Vivid, 1.22.x is not fit for local
charm development and testing because it is not systemd aware. We expect
to propose juju 1.24
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Devel Fix]
-
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Devel Fix]
-
Hi Robie.
I prepared a backport of 1.22.5 to trusting using the trusty-updates spb as a
base plus debian/* changes from the wily spb.
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.22.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Robie.
I prepared a backport of 1.22.5 to trusting using the trusty-updates spb as a
base plus debian/* changes from the wily spb.
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.22.5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The message Can not have partition outside/without disk indicates a
problem with the partition table.
To fix the problem you might look at the following article:
How-to Fix Invalid MSDOS Partition Tables
http://gparted.org/h2-fix-msdos-pt.php
--
You received this bug notification because you
** Changed in: juju-core
Status: Fix Released = Triaged
--
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
Hi Robie.
I updated the source package to include distro-info in build-depends.
lp:~sinzui/ubuntu/wily/juju-core/juju-1.22.5
This ensure juju can learn about every Ubuntu distro that is know to the host
system. I think this addresses the case where Ubuntu chooses to rebuild an old
package.
Hi Robie.
I updated the source package to include distro-info in build-depends.
lp:~sinzui/ubuntu/wily/juju-core/juju-1.22.5
This ensure juju can learn about every Ubuntu distro that is know to the host
system. I think this addresses the case where Ubuntu chooses to rebuild an old
package.
** Changed in: wildmidi (Ubuntu)
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/332877
Title:
After playing MIDI file, error File corrupt (Expected track
** 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/1393164
Title:
package libopenal1:amd64 1:1.14-4ubuntu1 failed to
I pushed the debian/copyright updates to lp:~sinzui/ubuntu/wily/juju-
core/juju-1.22.5. I hope this branch is suitable to make the wily
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462001
I pushed the debian/copyright updates to lp:~sinzui/ubuntu/wily/juju-
core/juju-1.22.5. I hope this branch is suitable to make the wily
package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
The src/github.com/juju/txn issue is fixed in commit
99ec629d0066a4d73c54d8e021a7fc1dc07df614 in upstream master
https://github.com/juju/txn/commit/99ec629d0066a4d73c54d8e021a7fc1dc07df614
The files are LGPL. Upstream juju is also switching to
src/github.com/juju/txn tip.
--
You received
The src/github.com/juju/txn issue is fixed in commit
99ec629d0066a4d73c54d8e021a7fc1dc07df614 in upstream master
https://github.com/juju/txn/commit/99ec629d0066a4d73c54d8e021a7fc1dc07df614
The files are LGPL. Upstream juju is also switching to
src/github.com/juju/txn tip.
--
You received
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
+ [Devel Fix]
+ [sinzui]
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
+ [Devel Fix]
+ [sinzui]
** Changed in: juju-core (Ubuntu)
Status: New = Invalid
--
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/1447200
Title:
juju-core 1.23.1 is not packaged in Ubuntu
To manage
** Changed in: juju-core (Ubuntu)
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/1447200
Title:
juju-core 1.23.1 is not packaged in Ubuntu
To manage notifications about
Public bug reported:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Development Fix]
Upload of new upstream
Public bug reported:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Development Fix]
Upload of new upstream
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
- [Development Fix]
-
-
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
- [Development Fix]
-
-
** Summary changed:
- juju ssh/scp commands cause spurious key errors
+ juju ssh/scp/run commands cause spurious key errors
** Also affects: juju-deployer
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- juju ssh/scp commands cause spurious key errors
+ juju ssh/scp/run commands cause spurious key errors
** Also affects: juju-deployer
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
just crashed
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bacula-director-mysql 5.2.6+dfsg-9.1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: i386
Date:
Public bug reported:
just crashed
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bacula-director-mysql 5.2.6+dfsg-9.1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic i686
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: i386
Date:
This looks like the following upstream bug report:
GParted 0.19.0-2 segfaults with error in Glib::wrap_register()
https://bugzilla.gnome.org/show_bug.cgi?id=743399
A patch to glibmm has been submitted and committed to glibmm upstream.
See bug report:
core dump in wrap_register() when calling
Can no longer reproduce, considering fixed.
** Changed in: wildmidi (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/332877
Title:
After playing MIDI file,
This should be fixed in 1.16 now available in Debian.
** Changed in: openal-soft (Ubuntu)
Status: New = 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/1393164
Title:
package
I do not want 1.22.1 going into updates because there is a compatibility
issue. Bug 1454829 is about a case were a 1.20.11 client cannot talk to
an env bootstrapped with. 1.22.x. The certificate rules are different,
preventing the client from talking. This is not an issue for envs
upgraded from
I do not want 1.22.1 going into updates because there is a compatibility
issue. Bug 1454829 is about a case were a 1.20.11 client cannot talk to
an env bootstrapped with. 1.22.x. The certificate rules are different,
preventing the client from talking. This is not an issue for envs
upgraded from
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
@Oleg, et al.
I understand that there is a plan to release a 1.22.4 soon. The intent is to
support this version as well as the current 1.23. There are orgs committed to
using 1.22 for some time and that there are stability fixes that are being
backported.
If we think that Ubuntu users don't
@Oleg, et al.
I understand that there is a plan to release a 1.22.4 soon. The intent is to
support this version as well as the current 1.23. There are orgs committed to
using 1.22 for some time and that there are stability fixes that are being
backported.
If we think that Ubuntu users don't
Juju requires a newer version of mongodb to address this issue, one that
supports the quiet flag. We can see that the packages with the required version
do not exist yet in.
http://www.mongodb.org/dl/linux/x86_64-ubuntu1404
There is nothing that can be done. The fix described in comment #9
Juju requires a newer version of mongodb to address this issue, one that
supports the quiet flag. We can see that the packages with the required version
do not exist yet in.
http://www.mongodb.org/dl/linux/x86_64-ubuntu1404
There is nothing that can be done. The fix described in comment #9
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** No longer affects: gdp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374297
Title:
Plugins cannot be activated from preferences - plugins
To manage notifications about this bug go to:
** No longer affects: gdp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306363
Title:
Session-Saver Plugin Missing from gedit-plugins
To manage notifications about this bug go to:
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
Ubuntu juju 1.22.1 on vivid is compatible with 1.22.x from upstream
Juju. It is suitable deploying and maintaining environments in public
and private clouds. Juju is compatible with the versions of quickstart
(and deployer) provide by Ubuntu main and proposed.
Note that 1.22.1 does not support
Ubuntu juju 1.22.1 on vivid is compatible with 1.22.x from upstream
Juju. It is suitable deploying and maintaining environments in public
and private clouds. Juju is compatible with the versions of quickstart
(and deployer) provide by Ubuntu main and proposed.
Note that 1.22.1 does not support
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
juju 1.22.0 is fit for purpose. The client can work with agents and
servers in public and private clouds. The Juju charm store only supports
LTS services. It is not possible to place a vivid charm in the store.
The only vivid users impaired by missing systemd support are charm
developers and
juju 1.22.0 is fit for purpose. The client can work with agents and
servers in public and private clouds. The Juju charm store only supports
LTS services. It is not possible to place a vivid charm in the store.
The only vivid users impaired by missing systemd support are charm
developers and
** Changed in: juju-core (Ubuntu)
Status: New = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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/1316272
Title:
juju destroy-environment =256 nodes fails
To manage
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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/1316272
Title:
juju destroy-environment =256 nodes fails
** Changed in: juju-core (Ubuntu)
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/1304407
Title:
juju bootstrap defaults to i386
To manage notifications about
** Changed in: juju-core (Ubuntu)
Status: Triaged = 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/1304407
Title:
juju bootstrap defaults to i386
To manage
** Changed in: juju-core (Ubuntu)
Status: New = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: New = 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/1302205
** Changed in: juju-core (Ubuntu)
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/1318366
Title:
jujud on state server panic misses transaction in queue
To
** Changed in: juju-core (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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/1250007
Title:
Bootstrapping azure causes memory to fill
To manage
** Changed in: juju-core (Ubuntu)
Status: Triaged = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Triaged = 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/1318366
Title:
jujud on state server panic misses
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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/1250007
Title:
Bootstrapping azure causes memory to fill
** Changed in: juju-core (Ubuntu)
Status: Triaged = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I tested juju 1.22.0 on vivid with streams and with quickstart (from
vivid). All is good. The client is good for working with all providers
and state servers on trusty and precise.
** Description changed:
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-
proposed, but
I tested juju 1.22.0 on vivid with streams and with quickstart (from
vivid). All is good. The client is good for working with all providers
and state servers on trusty and precise.
** Description changed:
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-
proposed, but
** Description changed:
We're now in a position to have 1.22.0 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 the tools in
their stable simplestream and announces the release for
** Description changed:
We're now in a position to have 1.22.0 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 the tools in
their stable simplestream and announces the release for
The details are also available immediately under the details section of
the Applying pending operations window.
For example, see The progress dialog on the GParted web site screenshots page.
http://gparted.org/screenshots.php
Following is an example of the details in the Applying pending
No worries Phillip. We all get busy from time to time. :-)
Steps to reproduce the crash are included in the upstream bug report. 'Still
it is always good to have the original reporter confirm if the problem is
resolved.
https://bugzilla.gnome.org/show_bug.cgi?id=735669#c4
If it helps to get
@Phillip, this report sounds very similar to the following upstream
report.
GParted crashes resizing fat16 file system
https://bugzilla.gnome.org/show_bug.cgi?id=735669
Mike Fleetwood posted a libparted patch to address the issue.
https://bugzilla.gnome.org/show_bug.cgi?id=735669#c15
Perhaps
@Skyman,
If you want to test to see if Mike's patch fixes the problem, the easiest way
is to try booting from the latest GParted Live 0.22.0-1.
http://gparted.org/livecd.php
The GParted Live image contains a custom parted/libparted that includes Mike's
patch.
--
You received this bug
A patch for this issue was included in the upstream GParted 0.22.0
release on March 23, 2015.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078445
Title:
Xubuntu install fail due partition auto
Public bug reported:
I was watching Episodes though the speakers for about an hour then, I
plugged in my headphone and Nothing was coming out
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname:
** 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/1409639
Title:
juju needs to support systemd for = vivid
To manage notifications
** 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/1409639
Title:
juju needs to support systemd for = vivid
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/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
I can confirm this in Comsol Multiphysics, and various versions of
eclipse and liclipse, on Kubuntu 14.04 64-bit. Really serious bug. The
Eclipses tend to crash during debugging but it seems random. Comsol used
to run for a while before crashing but now crashes as soon as you create
a new blank
Ok, changing the combobox appearance as detailed at
http://askubuntu.com/questions/513471/kubuntu-14-04eclipse-adt-crashes-
at-button-ok-from-project-properties/530468 fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
701 - 800 of 5893 matches
Mail list logo
