I would expect that in that situation that the security team would be
able to assist in downloading the correct package set/debs via a script
or list using curl or wget vs an install. The UA client does not perform
as a software downloader and is specific to setting up a system.
We know we have
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Incomplete => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for the log, it looks like we tried to get the cloud details
for the machine and it was empty. Can you share a bit of information on
what type of platform this was on? Is this on a machine, lxd container,
cloud instance on a specific cloud?
File
Thanks for the bug report. Do you have any interesting details in the
log file referenced?
/var/log/ubuntu-advantage.log
Marking incomplete while we collect information on what's failed.
Thanks!
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received
The reasoning is that FIPS is only for customers who need that specific
requirement. It requires using a kernel and other modules that are
certified and are therefore often slightly older than the latest
versions available in the release.
The lack of 20.04 versions is that Ubuntu images in the
We are working to get a fix released as 27.2.2 asap. The patch needed
is located here:
https://github.com/canonical/ubuntu-advantage-client/commit/9fe14e7b1ed78f1af7a7c9ba81a086f3a514687c
On Tue, Jul 27, 2021 at 12:15 PM Eric Barrera
<1938...@bugs.launchpad.net> wrote:
>
> I'm seeing this when
We'll work to release a hotfix with the landed PR asap.
On Tue, Jul 27, 2021 at 4:15 AM Pieter Houwen
<1936...@bugs.launchpad.net> wrote:
>
> When can we expect this to hit production? I just updated my WSL today
> and I stumbled across this error but I can see from the PR that it is
> already
Yes, this is intended. It is not assumed that every user with access to
a system can access credentials used to operate the software on the
system. It is assumed a user with root access can access those
credentials and provide source packages as might be required for
customer purposes.
** Changed
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has been resolved in later ua client updates and images should not
include these fixes. Marking fix released. Please let me know if you
continue to hit issues.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-advantage-tools (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/1927029
Title:
ua attach command fails
To manage notifications about this
Thank you for the feedback. We have debated the risk/reward of removing
things on upgrade, however since it doesn't do any harm and the end-user
has enabled a feature it can carry forward cleanly. Going in and running
a `ua disable esm-infra` after the user turned it on seemed a bit too
far and
$ cloud-init --version
cloud-init 0.7.8
Can you give us more background on that image you're using? Cloud-init
went to an annual naming convention in 2017 e.g. 17.1, 17.2 and is up to
21.1 currently. That seems to me like you've got a VERY outdated cloud-
init on this system? It should have been
It looks like an issue parsing the file: /var/lib/cloud/data/result.json
Are you able to look at share those contents as well? If there's
sensitive content I can mark this bug security private to assist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
"Also note that while 'base' and 'extra' might have been used before,
you might not have seen Seth's comment 7 that indicated it didn't turn
out very well for apparmor, so maybe 'base' and 'extra' aren't the best
names, even if they've been used before."
Thanks, I did see that and we discussed
Thanks for the feedback folks. We spent some time thinking through this
and the goals of the split and have come up with using -base and
-extras. There's some prior art to this in the archive and we don't want
to go with any naming convention that would indicate a "value" judgment
on the two
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926183
Title:
'ua fix' tells me to reboot with inaccurate message
Thanks for the report.
Yes I can see the reboot conflicting there. We generally are showing
that if the system indicates a reboot is required to try to get the user
to an all-green state, but here in ua fix it is distracting.
The fact that it says it was not resolved though is completely
Sorry, conflated the two issues.
Here the text structure I appreciate the feedback. We've currently
implemented the design and are eager to get feedback like this to drive
improvements to the design going forward.
Marking this as wishlist just for the purpose of taking various feedback
on output
Thanks for the report.
Yes I can see the reboot conflicting there. We generally are showing
that if the system indicates a reboot is required to try to get the user
to an all-green state, but here in ua fix it is distracting.
The fact that it says it was not resolved though is completely
Thanks for poking at the packaging bug. We've got a tracking bug on the
upstream source here:
https://github.com/canonical/ubuntu-advantage-client/issues/1300
We release a beta of the v26 client to the staging PPA yesterday:
https://launchpad.net/~ua-client/+archive/ubuntu/staging
This v26
@Tianon, yes we're tracking the upstream changes but are not finding
them sufficient to address the issue. We're finding we need more than
just that change to BindsTo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you are currently affected:
sudo systemctl restart docker
It looks like the packaging will stop docker when containerd is stopped, but
does not start it on start and that's dropped folks into this situation. We're
working out a fix for that.
--
You received this bug notification
I've migrated it here: https://github.com/canonical/ubuntu-advantage-
client/issues/1244. Marking this bug as won't fix as it's not so much a
package issue, but the upstream software functionality.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Won't Fix
--
You received
I think this is a really interesting idea. There's a vision for the tool
to be more useful as a general "state of the machine" and unattended-
upgrades would fit into this story. I'm migrating this bug to the
upstream project and will make sure to highlight the idea with the team
and see how this
I'm going to go ahead then and mark this as won't fix for cloud-init as
it's behaving as expected and we have the other associated bug to work
on improving the experience. I'll note this bug in a comment over there.
** Changed in: cloud-init (Ubuntu)
Status: New => Won't Fix
** Changed
The team has identified the upstream patch and will pull that down and
update it. We agree the current workaround will work ok and hold until
the updated package can be provided and have a test case and go through
the SRU process. I've added the tag that this bug blocks updates to the
package in
In our functional test we use Bionic images, and sure enough the netplan.yaml
[9]
written there does _NOT_ include the MTU! The OpenStack Metadata source
remains
the same [10].
Hmm, however it should be the same version of cloud-init in either
Bionic or Focal tests. Is this a netplan
Frode, can you explain to me the OpenStack operator path here. I'm not
familiar with how these adjustments are practically made.
You mention "a operator to reduce the MTU available to instances" and
"To maximize performance these clouds have configured their instances to
use the maximum available
We will SRU at some point but we don't have a current timeline.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Curtin doesn't handle type:mount entries without 'path' element
To
I believe we should check the exact current wording with Lech.
My personal opinion is we should drop the top line all together and just
keep the "Enable ... to receive 71..." and I would change the wording as
such:
Enable UA ESM for Infrastructure to receive 71 additional security updates.
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Triaged
** Changed in: cloud-init (Ubuntu)
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/158
We were originally waiting to get a Solutions QA verification for Xenial
however they are not able to perform those tests any longer. Given that
we're submitting with the CI and other testing attached to the bug. I'm
updating Xenial as verified.
** Tags removed: verification-needed-xenial
** Tags
Thank you for taking the time to report this issue. As you note, this is
a long-standing feature of Ubuntu that Canonical leverages to help
understand our user base and improve and prioritize work that makes
Ubuntu better for all. I can assure you that all information is GDPR
compliant and that we
** Changed in: ssh-import-id (Ubuntu)
Assignee: Canonical Server Team (canonical-server) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874909
Title:
ssh-import-id gives ERROR
Hi Pengpeng, we're pulling together some notes on the best way forward.
It seems this process you describe isn't ideal for your customers and we
want to put together the right plan that should work much more smoothly
for them.
--
You received this bug notification because you are a member of
Does this provide enough of an automated process for the requirements?
https://discourse.ubuntu.com/t/please-test-autoinstalls-for-20-04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803667
Title:
After discussing with the team and getting guidance from folks that know
systemd better we're going to write out files just to
/etc/systemd/system for our agents and mongodb services. We'll need to
also make sure that we have a series-upgrade step for OS's that get
dist-upgraded to focal and have
$ systemctl --version
systemd 244 (244-3ubuntu1)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2
default-hierarchy=hybrid
ubuntu@juju-e7323e-1:/etc/systemd/system$ systemctl status
The main issue is that Juju controllers need to retrieve the binaries it
runs from streams.canonical.com and that the client (typically running
on an operator laptop outside the cloud) needs to be able to reach the
controller API endpoints.
If you're getting an error during bootstrap about
This appears to have been addressed and not updated in 2.5 release as
well as a 2.4 release.
** Changed in: juju
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was addressed in https://github.com/juju/juju/pull/9491
** Changed in: juju
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/1804018
Title:
** Changed in: juju
Assignee: Richard Harding (rharding) => (unassigned)
** Changed in: juju
Milestone: 2.5-beta2 => 2.5.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Assigning to jam to shepherd through. The PR isn't yet complete but
discussion is going on in that PR towards a fix.
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => High
** Changed in: juju
Milestone: None => 2.5.0
** Changed in: juju
** Changed in: juju
Milestone: 2.5-beta1 => 2.5-beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Title:
bionic: LXD containers don't get fan network IP addresses
To manage
** Changed in: juju
Milestone: 2.5-beta1 => 2.5-beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798117
Title:
juju sends "network" top level key to user.network-config in lxd
containers
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Milestone: None => 2.5-beta1
** Changed in: juju
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju
Assignee: (unassigned) => Richard Harding (rharding)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Title:
bionic: LXD containers don't get fan network IP addres
** Changed in: juju
Status: Triaged => Incomplete
** Changed in: juju/2.3
Status: Triaged => Incomplete
** Changed in: juju/2.3
Milestone: 2.3.9 => 2.3.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju/2.3
Milestone: 2.3.9 => 2.3.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Title:
bionic: LXD containers don't get fan network IP addresses
To manage
** Changed in: juju
Milestone: 2.4.2 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784834
Title:
maas: incomplete bridge configuration for VLANs
To manage notifications about this bug
With that in mind I'm going to mark incomplete and if we come back from
the netplan folks that Juju should be doing something differently we can
narrow down and correct the issue on our end.
** Changed in: juju
Status: Triaged => Incomplete
--
You received this bug notification because
Tested w Juju 2.1 beta3 and verified I can get over 20 containers and
while it's slow does not get stuck in pending. The changes to the
profiles on the server that Michael has done appear to be working.
** Changed in: juju
Status: In Progress => Fix Committed
--
You received this bug
** Changed in: juju
Milestone: 2.1-beta4 => 2.1-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go to:
** Changed in: juju
Status: Triaged => 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/1640079
Title:
LXDs doesn't start after a reboot
To manage notifications about this bug go
The team is actively looking at the keys for the config in lp:1631254.
We'll verify that this is indeed the same issue but we're looking to
have this fix in for 2.1 final and should be ready for 2.1 RC1 after the
holiday break.
--
You received this bug notification because you are a member of
Also see lp:1536269 and lp:1644153 for additional background.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443704
Title:
Support for TLS 1.2 not present (added in 2.7.9)
To manage notifications
This effects us at Juju because we've removed TLS 1.0 support due to the
POODLE vulnerability. Because the default python does not support TLS
1.2 we have broken Python clients for Trusty users.
See lp:1644331
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: juju
Assignee: (unassigned) => Richard Harding (rharding)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640079
Title:
LXDs doesn't start after a reboot
To manage notificati
** Changed in: juju-core/1.25
Assignee: (unassigned) => Richard Harding (rharding)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612645
Title:
New EC2 region in India (ap-south-1 - Mum
Chatting with tych0 we were linked to:
https://github.com/lxc/lxd/blob/master/doc/production-setup.md
That notes a bunch of tweaks to run the system at scale. We need to
evaluate what items make sense to enable ootb, and what things are solid
for a prod lxd system but not a great idea for all
ju.conf file with:
fs.inotify.max_queued_events = 131072
fs.inotify.max_user_instances = 1024
fs.inotify.max_user_watches = 4194304
** Project changed: juju-core => juju
** Changed in: juju
Status: Invalid => Triaged
** Changed in: juju
Assignee: (unassigned) => Richard Harding (rharding)
** Changed in: juju
Milestone: 2.0-rc1 => 2.0-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475260
Title:
instances cannot resolve their own hostname
To manage notifications about this
** Changed in: juju
Milestone: 2.0-beta19 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475260
Title:
instances cannot resolve their own hostname
To manage notifications about this
** Changed in: juju
Milestone: 2.0.0 => 2.1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570660
Title:
Plugins not included in juju manpages
To manage notifications about this bug go to:
Moved to the charmstore-client at:
https://github.com/juju/charmstore-client/issues/90
** Bug watch added: github.com/juju/charmstore-client/issues #90
https://github.com/juju/charmstore-client/issues/90
** Changed in: charm-tools (Ubuntu)
Status: New => Invalid
--
You received this
** 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/1355813
Title:
Interface MTU management across MAAS/juju
To manage
** Changed in: juju-core/1.25
Milestone: None => 1.25.7
** Changed in: juju-core/1.25
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612645
Title:
New EC2 region
** Changed in: juju-core/1.25
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612645
Title:
New EC2 region in India (ap-south-1 - Mumbai)
To manage
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
** Changed in: juju-core (Ubuntu)
Status: Invalid => New
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
** Also affects:
Steve, comment #12 seems to imply we're ok with the way with the current
set. We've got a bug and task to split those out for Y. Did you want
another ok from Jamie on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
These updates were presented to slangasek and the point of the making
juju1 the default is the one point left that we requested feedback on.
Feedback from slangasek is that if we're not prepared to make juju1 the default
then:
"upon upgrade, juju == juju2; if you want juju1, run juju-1.$fwibble
These updates were presented to slangasek and the point of the making
juju1 the default is the one point left that we requested feedback on.
Feedback from slangasek is that if we're not prepared to make juju1 the default
then:
"upon upgrade, juju == juju2; if you want juju1, run juju-1.$fwibble
- adding a comment to the juju 2.0 FFe that clarifies that the juju
client is built and runs on all architectures, including 32bit.
Comment added under the heading Mongodb to this effect since that's
where the confusion derived from.
- document the process for avoiding a late stage FFe and
- adding a comment to the juju 2.0 FFe that clarifies that the juju
client is built and runs on all architectures, including 32bit.
Comment added under the heading Mongodb to this effect since that's
where the confusion derived from.
- document the process for avoiding a late stage FFe and
See bug https://bugs.launchpad.net/juju-core/+bug/1564622 for the fix in
Juju to properly output the messaging to the user.
** Description changed:
When upgrading to Xenial the new default Juju version is going to be
2.0.
Because 2.0 clients are not compatible with 1.X environments,
See bug https://bugs.launchpad.net/juju-core/+bug/1564622 for the fix in
Juju to properly output the messaging to the user.
** Description changed:
When upgrading to Xenial the new default Juju version is going to be
2.0.
Because 2.0 clients are not compatible with 1.X environments,
See https://bugs.launchpad.net/juju-core/+bug/1564622 for the reasoning
of this path.
--
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
See https://bugs.launchpad.net/juju-core/+bug/1564622 for the reasoning
of this path.
--
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/1564670
Title:
After upgrade Juju 1.X should
This will be a target for the Juju team to update and verify that the
stripping of the binary is safe and passes all testing. This requires
building in some gating based on if the binary is golang vs gccgo.
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in:
This will be a target for the Juju team to update and verify that the
stripping of the binary is safe and passes all testing. This requires
building in some gating based on if the binary is golang vs gccgo.
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in:
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as
Add item
- document the process for avoiding a late stage FFe and package upload
for 16.10
--
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
To manage notifications
In an IRC conversation with: stgraber, infinity, mgz
We agreed that the outstanding issues are the following:
- adding a comment to the juju 2.0 FFe that clarifies that the juju client is
built and runs on all architectures, including 32bit.
- move the juju binary metapackage suggest juju-1.25
Add item
- document the process for avoiding a late stage FFe and package upload
for 16.10
--
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/1545913
Title:
[FFe] juju-core 2.0
To
In an IRC conversation with: stgraber, infinity, mgz
We agreed that the outstanding issues are the following:
- adding a comment to the juju 2.0 FFe that clarifies that the juju client is
built and runs on all architectures, including 32bit.
- move the juju binary metapackage suggest juju-1.25
No, there is no KVM local provider in Juju 2.0. Product management has
made the determination that the lxd tool provides the needed
functionality for both the lxc and kvm use cases. lxd in Juju 2.0 will
be the answer.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
No, there is no KVM local provider in Juju 2.0. Product management has
made the determination that the lxd tool provides the needed
functionality for both the lxc and kvm use cases. lxd in Juju 2.0 will
be the answer.
--
You received this bug notification because you are a member of Ubuntu
As part of our exception, we're blocking the inclusion of two other
packages:
https://bugs.launchpad.net/ubuntu/+bug/1561043
https://bugs.launchpad.net/ubuntu/+bug/1561037
As we update Juju around this exception those will be effected and will
need to have some leeway in the process.
--
You
As part of our exception, we're blocking the inclusion of two other
packages:
https://bugs.launchpad.net/ubuntu/+bug/1561043
https://bugs.launchpad.net/ubuntu/+bug/1561037
As we update Juju around this exception those will be effected and will
need to have some leeway in the process.
--
You
I can verify that this is still the case in 16.04 using ke3rnel 4.3.0-5.
I can get the moues working with the added 10-evdev.conf updates but the
multi-touch fails so there's no two finger scrolling or two finger tap
for right click abilities in the latest kernel.
** Changed in: linux (Ubuntu)
Note that I can also verify the comment that I have a new device id with
the keyboard cover purchased and so there are two devices, mine is the
0x07e2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The touchpad in this machine needs module options proto=imps.
As a workaround we can put this in /etc/modprobe.d/psmouse.conf:
options psmouse proto=imps
We should add this to the kerenl quirks table.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package:
Curtis, did you have a bug filed I can look back at the history there? I
faintly recall the conversation but I don't remember if we had some
documentation/bug to go with it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Curtis, did you have a bug filed I can look back at the history there? I
faintly recall the conversation but I don't remember if we had some
documentation/bug to go with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We'd like to complete updating juju-quickstart to support a $JUJU env
variable to help enable and aid CI and testing. This would allow the
user to specify which Juju client to use which would open the doors to
testing quickstart on one system against several versions of Juju.
1 - 100 of 172 matches
Mail list logo
