@mwhudson, a new version of juju-core-1, 1.25.6, is being uploaded into
yakkety. I agree with the package removal, but given the extended
timeline for juju 2.0, it's possible yakkety retains juju-core-1. Let's
revisit this before FF. I definitely agree with not including it in Z.
--
You received
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release exception
I've restored the debhelper script to version 7 as released. The
juju-1-default.links file was present in my version, heh, but not added
and thus not in the repository. This too has been corrected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
The current package in ubuntu is old and the maintainer is no longer
able to maintain the package. I'd like to request we replace this
package with the debian version which is newer and has a maintainer.
** Affects: golang-juju-loggo (Ubuntu)
Importance: Undecided
** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
** Description changed:
Juju 1.25.6 is a stable update containing critical bug fixes, including
MAAS compatibility, for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including for major vers
*** This bug is a duplicate of bug 1611855 ***
https://bugs.launchpad.net/bugs/1611855
Public bug reported:
Juju 1.25.6 is a stable update containing critical bug fixes, including
MAAS compatibility, for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including
** Summary changed:
- [SRU] Juju 1.25.6
+ [SRU] Juju 1.25.6 for trusty
** Branch unlinked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
** Branch linked: lp:~juju-qa/ubuntu/yakkety/juju/juju-1.25.6
** Branch linked: lp:~juju-qa/ubuntu/trusty/juju/juju-1.25.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611855
Title:
[SRU] Juju 1.
Public bug reported:
Juju 1.25.6 is a stable update containing critical bug fixes, including
MAAS compatibility, for the 1.25 series.
[SRU Information]
juju-core has a stable release exception, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.
[Impact]
This update brings
I have a lemu5 installed with Xubuntu 16.04. I have seen the same kind
of screen wrapping when I try to use the modesetting driver in place of
xserver-xorg-video-intel (as suggested by its description). It manifests
itself somewhat randomly during normal use. I noticed it is particularly
bad when y
Public bug reported:
package qemu-user-static 1:2.5+dfsg-5ubuntu10.2 failed to
install/upgrade: package qemu-user-static is not ready for configuration
cannot configure (current status 'half-installed')
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: qemu-user-static 1:2.5+dfsg-5ubuntu1
Verified I can bootstrap, the gui is pulling the correct version, lxd
and aws all work. Looks good.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Changed in: juju-core (Ubuntu)
Status: Fix Released => 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/1604137
Title:
[SRU] Juju 2.0 beta12 for Xenial
To manage notifications ab
Binary is present
$ ls /usr/lib/juju/mongo3.2/bin
mongo mongod mongoperf mongos mongosniff
I could invoke the binary
$ /usr/lib/juju/mongo3.2/bin/mongo
MongoDB shell version: 3.2.4
apt-cache show juju-mongodb3.2
Package: juju-mongodb3.2
Priority: optional
Section: universe/database
Installed
** Description changed:
- Admins and developers are unable to access to the juju mongodb instance
- to investigation issues.
+ [Impact]
+ Admins and developers are unable to access to the juju mongodb instance to
investigation issues.
The mongo client is built, but not included in the juju-
It should be noted we were forced to disable one test as it fails on
some architectures due to https://bugs.launchpad.net/juju-
core/+bug/1605313. As we've released the final tarball for beta12, we'd
like to land this SRU and continue working on squashing that bug
completely in the future.
--
You
It sounds like the "fix" for this lies outside of LXD. Can we add the
affected packages and involve the right upstreams for this? Are we going
to pursue this purely upstream with systemd / kernel or are we going to
attempt a distro-patch of some sort?
--
You received this bug notification because
** Changed in: juju-core (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/1508122
Title:
please transition to shared libraries
To manage notifications about th
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release exception
Marking invalid due to presence of beta12 which will go into yakkety /
xenial.
** Changed in: juju-core (Ubuntu)
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/1596920
Marking invalid due to presence of beta12 which will go into yakkety /
xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596920
Title:
Juju 2.0-beta10 in ubuntu
To manage notifications about t
** Also affects: trusty-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583740
Title:
mongo client is missing
To manage notifications about this
** Changed in: golang-golang-x-oauth2 (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568165
Title:
[MIR] golang-golang-x-oauth2
To manage notifications
** Changed in: golang-gopkg-mgo.v2 (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568162
Title:
[MIR] golang-gopkg-mgo.v2
To manage notifications about
** Changed in: golang-github-natefinch-lumberjack (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568168
Title:
[MIR] golang-github-natefinch-lumberjack
** Changed in: golang-google-api (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568163
Title:
[MIR] golang-google-api
To manage notifications about thi
So src/github.com/juju/juju/etc/bash_completion.d/juju2 is indeed the
cause of the failure. It's not clear why the file was renamed, but I've
added a packaging rule to swap the name so it installs into /usr/share
/bash-completion/completions/juju-core. We should fix upstream if
possible.
In my tes
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532935
Title:
Nodes stuck at grub menu when attempting to deploy
To manage
I have installed the proposed package on trusty and verified its
functionality.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stabl
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release exception
I have this same issue with fast playback and the same error message
ALSA lib pcm.c:7905:(snd_pcm_recover) underrun occurred
Ubuntu 15.10
Audacity 2.0.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
R610 system information
- BIOS ver: 6.4.0
- iDRAC 6 ver: 2.85 (Build 04)
- Lifecycle Controller Firmware ver: 1.7.5.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577722
Title:
MAAS 2.0.0 cannot
Some more information I recorded today from testing
- Any "Commission" or "Deployment" action from MAAS (triggered via IPMI v2)
causes the server to go into a erratical reboot loop
- After some reboot cycles (4-5) the server powers off.
- This behavior is present to 3 other R610 servers with exac
Hi Andres,
It's a Dell machine, so IFAIK they don't come with HPDSA/HPVSA arrays -
but I might be mistaken.
It has a PERC Raid controller, with only 1 300GB SAS drive (no RAID
config)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
WebGui Event Log
** Attachment added: "WebGUI Event Log"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1577722/+attachment/4654357/+files/EventLog-WebGui.txt
** Description changed:
Hi,
I run to an issue where MAAS 2.0.0 (beta3+bzr4941) cannot commission my
Dell PowerEdge R61
Public bug reported:
Hi,
I run to an issue where MAAS 2.0.0 (beta3+bzr4941) cannot commission my
Dell PowerEdge R610 servers. Nodes get enlisted correctly, but
commission fails. All other nodes in the same network, (IBM and HP) are
commissioned and deployed without any issues.
Commissioning dis
@Timo, ahh! Hence the fascination with unetbootin. Makes sense now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530530
Title:
Installer doesn't show up on some Chromebook
To manage notifications
Timo, this only affects newer releases. 14.04 works with the workaround
mentioned. The issue is indeed the resolution and 3:2 scaling I'd guess.
There's no graceful fallback either and you have to workaround it or
patch even after installed.
--
You received this bug notification because you are a
Public bug reported:
See
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
Since we want to support multi-release from the same branch, let's make
sure we adopt using the release name in strings as well.
** Affects: juju-core (Ubuntu)
Importance: Undecided
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU post-
- xenial release. This updates juju to the lastest 2.0 milestone version,
- beta5.
-
+ xenial release. This updates juju to t
** Summary changed:
- [SRU] Juju 2.0 beta5 for Xenial
+ [SRU] Juju 2.0 for Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573176
Title:
[SRU] Juju 2.0 for Xenial
To manage notifications abo
Public bug reported:
Ubuntu 16.04 Xenial
using ubuntu-vm-builder and having virtio_net = true in .cfg all of my
vm get ens# naming from the introduced Meaningful naming. The vm builder
just places the config in /etc/network/interfaces as eth0 without regard
to the actual beginning name.
** Affec
** Changed in: juju-core (Ubuntu Xenial)
Status: Triaged => Fix Released
** 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/1
** Description changed:
Doing Release upgrade from 14.04 to 16.04, mysql-5.7-server/mysql-server
failed during post-installation.
Before upgrade:
lsb_release -rd
Description: Ubuntu 14.04.4 LTS
Release: 14.04
After upgrade:
lsb_release -rd
Description: Ubuntu 16.04 LTS
R
Public bug reported:
Doing Release upgrade from 14.04 to 16.04, mysql-5.7-server/mysql-server
failed during post-installation.
Before upgrade:
lsb_release -rd
Description: Ubuntu 14.04.4 LTS
Release: 14.04
After upgrade:
lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
apt
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU post-
xenial release. This updates juju to the lastest 2.0 milestone version,
beta5.
[SRU Information]
juju-core has a stable release ex
Public bug reported:
We should have a vcs:bzr entry in debian/control
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Some logs for your perusal. unity8.log did not exist.
** Attachment added: "logs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1320356/+attachment/4640891/+files/logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
We fixed bug 1564622, along with creating a juju-1-default package in
xenial to alleviate this issue. Juju 2.0 is the default /usr/bin/juju
and will remain as such in Xenial, regardless of the installation path.
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-c
Packaging has been updated and tested with all packages in main. Juju in
xenial should depend on the packages in main listed above with the next
upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
** Description changed:
As part of acceptance into main for juju2, we need to ensure our package
depends on everything we can that is already in the archive. See bug
1545913 for the FFe.
This bug will track our dependencies to ensure we meet this requirement.
- Currently we need to a
mterry, the ubuntu server team should be the team bug subscriber. I
added canonical-juju-qa as we are helping package this, and thus it
makes it easier for us to also keep track during this process. Sorry for
the confusion.
On the test front, mongodb has had some packaging work done during
xenial
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package whic
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package whic
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package whic
@vorlon, yes you are correct, nothing is changing on that front. I've
simply added the juju-qa team as well so we can also keep an eye on
things during this process.
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency
** Description changed:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package whic
** Description changed:
As part of acceptance into main for juju2, we need to ensure our package
depends on everything we can that is already in the archive. See
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913 for the
FFe.
This bug will track our dependencies to ensur
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be used
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be used
For juju, we still need to ensure our MIR's are reviewed and land into
main, and that our packaging utilizes all possible dependencies that are
already in the archive. This work is targeted before release and is
being tracked in bug 1568148.
--
You received this bug notification because you are a
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be used
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be used
Public bug reported:
[Availability]
Source-only package currently available in universe.
[Rationale]
Build-dependency for juju. This is part of our on-going work for bug 1508120,
to stop bundling our dependencies in our source package.
[Security]
This is a source package which will only be used
Public bug reported:
As part of acceptance into main for juju2, we need to ensure our package
depends on everything we can that is already in the archive. See
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913 for the
FFe.
This bug will track our dependencies to ensure we meet this
** Changed in: juju-core
Milestone: None => 2.0.0
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Tags added: docteam juju-release-support
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564165
Title:
Credentials file displays unhelpful message for syntax errors
To
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564157
Title:
juju list-credentials fails to display
To manage notifications ab
** 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/1561633
Title:
help should work properly with alternatives
To manage notifications abou
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564168
Title:
juju list-credentials --show-secrets does not display passwords
T
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564670
Title:
After upgrade Juju 1.X should still be the default
To manage noti
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564163
Title:
environment name in credentials file is not a tag
To manage notif
Here's the ppa with the packages:
https://launchpad.net/~nskaggs/+archive/ubuntu/juju/+packages
And here's the status for each dependency mentioned.
http://paste.ubuntu.com/15569917/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Jamie, the additional packages are:
golang-github-altoros-gosigma
golang-github-dustin-go-humanize
golang-github-gabriel-samfira-sys
golang-github-gosuri-uitable
golang-github-joyent-gocommon
golang-github-joyent-gomanta
golang-github-joyent-gosdc
golang-github-joyent-gosign
golang-github-mattn-go
Adam has built the initial version desired for upload:
https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[FFe] juju-core 2.0
T
Public bug reported:
juju list-credentials --show-secrets does not display password data,
unless used with --format yaml.
The following commands all fail to show additonal information using
--show-secrets
juju list-credentials --show-secrets
juju list-credentials --format json --show-secrets
juj
Public bug reported:
If credentials.yaml contains invalid syntax, the error is
ERROR credentials.blarhg.google.credentials: expected string, got map
which does not accurately convey 'blarhg' is not valid syntax.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
It would be nice to include a tag of the environment name from my
credentials file.
aws:
default-credential: balloons
balloons:
auth-type: access-key
access-key: XXXxxx
secret-key: xxx
Given those credentials, I expect
Public bug reported:
When a cloud is not found in your credentials file, the credentials are
not listed. In addition, the credentials error given is confusing, and
non-consistent.
nskaggs@pixel:~$ juju list-credentials
ERROR removing secrets from credentials for cloud maas18: cloud maas18 not fou
This package is sitting in the xenial upload queue, ready for review.
The upload has been blocked upon juju2 landing into xenial, and thus
should be considered for an exception to missing the upload window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
This package is sitting in the xenial upload queue, ready for review.
The upload has been blocked upon juju2 landing into xenial, and thus
should be considered for an exception to missing the upload window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Description changed:
- The Juju team is preparing for a 2.0-beta1 release in time for the
- xenial feature freeze date (18-Feb), but not all features required for
- 2.0 will be ready by that date. We believe we will have a complete and
- stable Juju 2.0 by the time of the xenial release, but w
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561210
Title:
juju-core should depend on python3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
Public bug reported:
When calling help using juju2 directly, it refers to using the commands
as 'juju', rather than juju2. The help should be dynamic as well with
the alternatives packaging so when juju2 help is called directly, it
also specifies the use of juju2.
** Affects: juju-core (Ubuntu)
I've added 12 dependencies for the go modules used by juju as depends in
in the control file. This is a step back in the proper direction. There
are a couple more depends we could add based upon what's in the archive
that is currently breaking the build (one of them is lxd). Beyond that,
we'll need
Public bug reported:
Juju needs to depend solely on python3, not python2. Python2 is targeted
for removal from the images, and the quest continues to lower our
python2 dependencies.
https://blueprints.launchpad.net/ubuntu/+spec/foundations-x-python3-only
** Affects: juju-core (Ubuntu)
Impor
Public bug reported:
When the clocksource is set to "refined-jiffies" it ticks twice as fast.
This is not an issue when it is changed to "tsc".
The problem existed in earlier kernels too.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-76-generic 3.13.0-76.120
ProcVersio
To confirm the fix, checkout rev 763 of lp:ubuntu-calendar-app, and run
the
calendar_app.tests.test_new_event.NewEventTestCase.test_new_event_must_start_with_default_values.
It's a short test, and should fail without the change, and work with it.
--
You received this bug notification because you
Public bug reported:
The autopilot helper for optionselector seeks Label delegates, rather than
UCLabel delegates.
--
def get_selected_text(self):
"""gets the text of the currently selected item"""
option_selector_delegate = self.select_single(
'OptionSe
Jamie, I thought we had dropped all the fakeenv rules for autopilot?
Indeed we did switch to the notion of having dedicated devices that we
manually curate into known states before testing.
So all rules that support faking envs or mocking for autopilot can be
removed.
--
You received this bug no
On my system (Linux Mint Cinnamon), the icons do not differ between
maximised and non-maximised state - except that, irritatingly, the
hovered-over version of the maximise icon is *very dark* when the window
is maximised.
I wonder whether the poster means 'low contrast (grey and white) when
*the w
So... after ~6.5 years; 267 posts; and several thousand lines of
unhappy, frustrated, and/or annoyed feedback, my man page is still lying
to me about -t actually doing something and the devs are now adding
"you can use someone else's software or write your own" to justify their
design decision. Di
See also: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
keyboard/+bug/1542224
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536361
Title:
When using the sdk helper for the keyboard to type in a
Are we sure this isn't 'by design'? Can you prove it's a regression from
earlier releases?
** Changed in: nautilus (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/bu
** Changed in: debconf (Ubuntu)
Status: Triaged => Invalid
** Changed in: debconf (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/349469
Title:
deb
Had to register via web form rather than software due to captcha issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1033598
Title:
the CAPTCHA challenge in Ubuntu Software Center is much too diffi
** No longer affects: ubuntu-manual-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531226
Title:
While the installer is open gnome poweroff button doesn't work
To manage notifications about t
And I just remembered that I have some logs from the newer failure that
might help. I will post short excerpts here as otherwise there is
nothing to distinguish them from the logs of the older failure.
>From kern.log:
Nov 29 11:36:53 hydra kernel: [ 35.815890] bbswitch: version 0.7
Nov 29 11:36
More information: I found that 352.63 also claimed to support my nvidia
graphics card. I installed it. It made me reconfigure my xorg.conf.
Putting "Intel" as the default driver allowed me to see the login screen. But
whenever I entered the correct password, X would crash and send me back to the
601 - 700 of 2550 matches
Mail list logo
