[Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec

@chihchun see bug 1879389 for the apport dump. Because the kernel logs fill up with WARN_ON(intel_wait_for_register(...))/hsw_wait_for_power_well_enable it's hard to find specific other issues. I have observed the sound driver being crashy/sad on the same hardware but it's possibly improved with

[Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

Well, similar experience for me today, booted and logged in okay, but then the desktop session died leaving monitor backlight and keyboard lights on, but no other sign of life. Shutting lid to suspend then resume didn't help, had to hard power off. Then on next boot, it hung after login, but

[Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

Okay, pretty sure have found the right upstream bug, and have what looks like a good workaround. $ gsettings set org.gnome.settings-daemon.plugins.xsettings antialiasing 'grayscale' https://gitlab.freedesktop.org/mesa/mesa/issues/2183 The steps to reproduce does kill the session with a gpu hang

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

Captured one, context from journalctl: May 21 14:13:51 xps2020 kernel: [drm] GPU HANG: ecode 11:0:0x85db, in Xorg [1985], reason: hang on rcs0, action: reset May 21 14:13:51 xps2020 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 May 21 14:13:54 xps2020 kernel: Asynchronous wait

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

>From similar-but-maybe-not-the-same drm issues, seems capturing the GPU crash dump (if there is one) would be useful https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/2 https://gitlab.freedesktop.org/drm/intel/issues/673 I have a dmesg full of "WARNING ... [i915]" but no gpu

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

Both posted journalctl logs feature sections like this: May 21 11:03:29 asgard kernel: [drm] GPU HANG: ecode 11:0:0x85db, in Xorg [2421], reason: hang on rcs0, action: reset May 21 11:03:29 asgard kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 May 21 11:03:37 asgard kernel: i915

[Bug 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]

I am experiencing similar issues with a brand new Dell Inc. XPS 13 9300/077Y9N. Perhaps this bug should be renamed for the symptoms and user impact, as there are bunch of linked bugs for specific crashes related to packages? @vanvugt If it's helpful, I have also uploaded (with some struggle

[Bug 1604988] Re: Inconsistent licence in github.com/juju/utils/series

The file headers for this package should be changed to say LGPL, which I believe is the choice we made for all library-type projects from juju. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604988

[Bug 1613864] Re: Missing "juju-2"/"juju2" command.

Ideally we don't have that many aliases for the same thing (and some of those /usr/bin files are not from our latest packaging)? I think what you really want is to just run `/usr/bin/juju` but realise having juju-1-default makes that more complicated as well. So, I see some benefit in a

[Bug 1570650] Re: Use juju-mongodb2.6 for 1.25 on xenial

Per the upstream support policy: 2.4 has been end of life since March, so I'm not sure we can won't-fix this without a serious discussion about what our plans for supporting Juju 1.25 over the coming years are. That said, 2.6 will soon be in the same

[Bug 1564662] Re: Juju binaries should be stripped

** Changed in: juju-core Status: Triaged => Fix Released ** Changed in: juju-core Milestone: 2.1.0 => 2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564662 Title: Juju binaries

[Bug 1604988] [NEW] Inconsistent licence in github.com/juju/utils/series

Public bug reported: The per-file copyright headers in the series/ package of the juju/utils project all state: // Licensed under the AGPLv3, see LICENCE file for details. However the top level LICENCE file is LGPLv3 with exception. This confuses the issue for distribution. ** Affects:

[Bug 1600257] Re: Broken bash completion with old ppa packages present

Thinking about it, CI debs of that vintage should do, eg: Can try installing on of those in a fresh vm then installing new packaging over the top. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1600257] Re: Broken bash completion with old ppa packages present

Old versions of the ppa packaging, eg: -- You received this bug notification because

[Bug 1600257] Re: Broken bash completion with old ppa packages present

Hm, does it count as a purge-removed only conf file even if was placed there by dh_install as part of override_dh_auto_install in rules? If that's the case, what do you recommend we do to clean up? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1600257] Re: The tab completion on juju yields KeyError: 'services'

I think all we really want to do is make sure we conflict correctly with the old ppa package names, then dpkg will handle the removal of the old completion files before starting the install of the new juju-2.0 package. ** Summary changed: - The tab completion on juju yields KeyError: 'services'

[Bug 1600257] Re: Broken bash completion with old ppa packages present

See irc log for more context: In particular, the completion files come from multiple old ppa packages: juju2: /etc/bash_completion.d/juju2 juju-core2: /etc/bash_completion.d/juju-core2

[Bug 1600311] Re: Juju 2.0 Bootstrap Fails on Ubuntu Trusty Power machine.

The interesting problems here all seem to be at the lxd level, from the second log in comment #2: lxc 20160714064249.306 INFO lxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:238 - changed apparmor profile to lxd-juju-47a009-0_ lxc 20160714064249.306 ERRORlxc_seccomp -

[Bug 1600257] Re: The tab completion on juju yields KeyError: 'services'

Part of the issue here is having a mix of ppa packages and archive packages leads to a bunch of bash completion files on disk that may not correspond to the correct version of juju. We should make our conflicts/replaces robust on the ppa and archive packages so users can't have old ppa versions

[Bug 1600257] Re: The tab completion on juju yeilds KeyError: 'services'

** Also affects: juju-core (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/1600257 Title: The tab completion on juju yields KeyError: 'services'

[Bug 1596920] [NEW] Juju 2.0-beta10 in ubuntu

Public bug reported: New upstream release 2.0-beta10 should be packaged in yakkety. The 2.0 version of juju is still not quite final, see FFE bug 1545913 for Xenial for background. The agreement was we would include upstream releases as they came in the development version of juju, and SRU back

[Bug 1570657] Re: Bash completion needed for versioned juju commands

** Tags added: bash-completion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to:

[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas

** Tags added: bash-completion packaging ** Changed in: juju-core Importance: Undecided => High ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Milestone: None => 2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas

Basic problem seems to be the naming of the file under /usr/share/bash- completion/completions/ - currently the juju 2.0 packages have it as 'juju2' which bash won't invoke for the `juju` name. However, the script is not (yet) relevantly different from the juju 1.25 bash completion, so older

[Bug 1588403] Re: Tab completion missing in Juju 2.0 betas

** Also affects: juju-core (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/1588403 Title: Tab completion missing in Juju 2.0 betas To manage

[Bug 1538764] Re: needs dependency on python-novaclient

Versions of juju < 1.0 are long out of support, and juju in ubuntu does not require novaclient to work with openstack. ** Changed in: juju Status: New => Won't Fix ** Changed in: juju (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member

[Bug 1576318] Re: juju register not clear that you're creating a new password

** Also affects: juju-core Importance: Undecided Status: New ** Tags added: usability ** Changed in: juju-core Importance: Undecided => Medium ** Changed in: juju-core Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1570657] Re: Bash completion needed for versioned juju commands

** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title: Bash completion needed for versioned juju commands To manage notifications about this bug go to:

[Bug 1576778] Re: juju2 tab-completion for sub commands is broken in beta6

*** This bug is a duplicate of bug 1570657 *** https://bugs.launchpad.net/bugs/1570657 Thanks, see the existing bug (on juju-core in ubuntu, confusing), for this. ** This bug has been marked a duplicate of bug 1570657 Bash completion needed for versioned juju commands -- You received

[Bug 1576241] Re: juju returns command not found with no helpers

Looks like the command-not-found-data package was last updated before the new juju package got out of proposed: command-not-found (0.3ubuntu16.04) xenial; urgency=medium *

[Bug 1574076] Re: juju package should suggest juju-1.25 not juju-core

The Suggests is dual purpose for Xenial. Both does the normal job of informing the user of the new juju 1.X specific package, but is also a tricky upgrade hack. The release team noted that the upgrade process now autoremoves packages in its default behaviour, so going to Xenial and 2.0 juju would

[Bug 1571072] Re: autopkgtest future-manual-provider fails on armhf for 2.0

For this case, skipping this particular test on 32 bit arches is the right thing. ** 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.

[Bug 1570654] Re: Manpage still refers to 1.X config for 2.0

** Changed in: juju-core 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/1570654 Title: Manpage still refers to 1.X config for 2.0 To manage notifications

[Bug 1570759] Re: apt-get install juju does not install /usr/bin/juju

Please run apt-get update and apt-get upgrade, this issue should now be resolved. We have a few pending changes to make the first upgrade experience clearer, for now note that you can run 1.25 with the 'juju-1' name, and 'juju' will be 2.0. ** Changed in: juju-core Status: Triaged => Fix

[Bug 1570654] Re: Manpage still refers to 1.X config for 2.0

Fix proposed: ** Changed in: juju-core 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/1570654 Title: Manpage still

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

I have some changes from Friday to address these test failures and the armhf one, that I've now committed and put in the packaging branch: As the lxd changes

[Bug 1545913] Re: [FFe] juju-core 2.0

The juju-core-1 autopkgtests are all green: We have bug 1570759 reported for the slightly weird state of the xenial archive with 1.25.5 in main but 2.0-beta4 stuck in proposed. I filed a bunch of bugs. The autopkgtest problems for 2.0:

[Bug 1571082] [NEW] autopkgtest lxd provider tests fail for 2.0

Public bug reported: The new autopkgtests for the lxd provider are still not passing yet. The bridge setup looks like it works, but when juju comes to try and connect to lxd it is rejected on an http url.

[Bug 1571072] [NEW] autopkgtest future-manual-provider fails on armhf for 2.0

Public bug reported: The current-manual-provider test passes everywhere, which relies on setting up a state server in place in the same test vm. However, on armhf only the future-manual-provider variant, which first munges the machine series to emulate the next development release, fails.

[Bug 1545913] Re: [FFe] juju-core 2.0

Well, mixed news. The 1.25.5 upload yesterday got bopped by the keyserver failing, but has now been reuploaded and we're waiting on the autopkgtest run. The 2.0-beta4 upload happened, and we have test results: Things are in a better state

[Bug 1570759] Re: apt-get install juju does not install /usr/bin/juju

** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** No longer affects: juju-release-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570759 Title: apt-get

[Bug 1570660] [NEW] Plugins not included in juju manpages

Public bug reported: Currently juju plugins neither have their own manpages, nor are they included in the main juju manpage. There is also not a `juju plugins` command or similar, so installed plugins are completely undiscoverable from the command line. If we give each plugin an autogenerated

[Bug 1570657] Re: Bash completion needed for versioned juju commands

There's a pending pull request for other 2.0 improvements to the bash completion script here: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570657 Title:

[Bug 1570657] [NEW] Bash completion needed for versioned juju commands

Public bug reported: The new juju packaging in xenial includes 'juju-1' and 'juju-2.0' commands that are currently not covered by the bash-completion script. This means no completion for 1.X is available at all at present, and is otherwise confusing when needing to use the specific version

[Bug 1570654] [NEW] Manpage still refers to 1.X config for 2.0

Public bug reported: The 2.0 manpage still includes text about environments.yaml and nothing about new configuration files: FILES ~/.config/juju/environments.yaml This is the Juju config file, which you can use to specify mul‐ tiple models in which to deploy.

[Bug 1570651] Re: Manpages for juju aliases drop version

** Tags added: docs ** 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/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to:

[Bug 1570651] [NEW] Manpages for juju aliases drop version

Public bug reported: With xenial, we now provide juju version specific wrappers named 'juju-1' and 'juju-2.0' that have corresponding manpages. However, the text inside the pages just uses 'juju' as the name, not the alias, which is particularly confusing for juju-1 where the commands will often

[Bug 1570650] [NEW] Use juju-mongodb2.6 for 1.25 on xenial

Public bug reported: Now xenial has a juju-mongodb2.6 package that has better support expectations than our existing (2.4) juju-mongodb package, we should install and use that by preference for the local provider. * The juju-local package should depend on juju-mongodb2.6 instead of juju-mongodb

[Bug 1545913] Re: [FFe] juju-core 2.0

Have updated packaging and upstream for both juju 2.0 and 1.25 ready to upload. https://code.launchpad.net/~juju-qa/ubuntu/xenial/juju/juju-1.25.5 New 1.25.5 bugfix release. Fixed the adt tests, including making them run with isolation-container rather than isolation-machine. adt-run

[Bug 1545913] Re: [FFe] juju-core 2.0

...and I refresh the page and see someone has now reviewed both mongodb packages. Thanks! -- 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

[Bug 1545913] Re: [FFe] juju-core 2.0

Sorry, should have been clearer. Yes, I am working on fixing those issues with the tests. We're also trying to get a new source release this week that can be put the the archive, this package can't move forward without that. "LXD v2.0.0-rc8 does not work with Juju v2.0-beta3"

[Bug 1545913] Re: [FFe] juju-core 2.0

It seems juju-core-1 is just stuck on the juju-mongodb2.6 package lying around unreviewed in the new queue: juju-core-1 (- to 1.25.4-0ubuntu5) Maintainer: Ubuntu Developers Section:

[Bug 1545913] Re: [FFe] juju-core 2.0

Sadly, being stuck in -proposed is probably correct for beta3, due to the above mentioned lxd breakages. Note that the future-lxd-provider gets futher, but still breaks due to changes in lxd since the test was last modified with beta2: + lxd-images import ubuntu yenial --alias ubuntu-yenial

[Bug 1545913] Re: [FFe] juju-core 2.0

> - juju-2.0 is shipping a link named 'juju-upgrade-mondo' instead of > 'juju-upgrade-mongo'. This probably needs fixing. Fixed in the packaging branch. > - juju-2.0 uses and src/github.com/lxc/lxd/ (expected) and does not > build-depend on the golang-github-lxc-lxd-dev package in the

[Bug 1545913] Re: [FFe] juju-core 2.0

Packaging branches have been updated based on review feedback, new versions need uploading: lp:~juju-qa/ubuntu/xenial/juju/juju-1.25.4 lp:~juju-qa/ubuntu/xenial/juju/xenial-2.0-beta3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1545913] Re: [FFe] juju-core 2.0

The proposed packaging updates are now available in Adam's PPA: This includes: * Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand * Use of Suggests to keep Juju 1.X tools around through upgrade from

[Bug 1545913] Re: [FFe] juju-core 2.0

The proposed packaging updates are now available in Adam's PPA: This includes: * Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand * Use of Suggests to keep Juju 1.X tools around through upgrade from

[Bug 1564670] [NEW] After upgrade Juju 1.X should still be the default

Public bug reported: 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, this means existing environments will be inaccessible unless the 1.X client is switched to. The plan is to give a warning when creating

[Bug 1564670] [NEW] After upgrade Juju 1.X should still be the default

Public bug reported: 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, this means existing environments will be inaccessible unless the 1.X client is switched to. The plan is to give a warning when creating

[Bug 1564662] [NEW] Juju binaries should be stripped

Public bug reported: Previously the juju team has been asked to strip the go binaries in the distro packaging. Per bug 1265970 that was not possible as with go 1.2 it introduced bugs such as bug 1200255. With go 1.6 in xenial, it may now be safe to strip the juju binaries, but this needs testing

[Bug 1564662] [NEW] Juju binaries should be stripped

Public bug reported: Previously the juju team has been asked to strip the go binaries in the distro packaging. Per bug 1265970 that was not possible as with go 1.2 it introduced bugs such as bug 1200255. With go 1.6 in xenial, it may now be safe to strip the juju binaries, but this needs testing

[Bug 1545913] Re: [FFe] juju-core 2.0

I've edited the bug the clarify the juju-mongodb situation. There's a change to both tweak the version of mongodb and make the unit tests more reliable, which was held from landing for beta3 waiting on the package in ubuntu. It will be included in the rc. -- You received this bug notification

[Bug 1545913] Re: [FFe] juju-core 2.0

I've edited the bug the clarify the juju-mongodb situation. There's a change to both tweak the version of mongodb and make the unit tests more reliable, which was held from landing for beta3 waiting on the package in ubuntu. It will be included in the rc. -- You received this bug notification

[Bug 1545913] Re: [FFe] juju-core 2.0

** 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

[Bug 1545913] Re: [FFe] juju-core 2.0

** 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

[Bug 1545913] Re: [FFe] juju-core 2.0

Updated the description with the example upgrade testing using the test packages in the ppa. ** 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

[Bug 1545913] Re: [FFe] juju-core 2.0

Updated the description with the example upgrade testing using the test packages in the ppa. ** 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

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

Hm, looks like the adventures with reworking the packaging yesterday (which I didn't follow the reasoning behind, but ended up basing the beta2 packaging branch on an existing xnox branch) lost the Build- Depends we had on archive golang packages. What we had:

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

Hm, looks like the adventures with reworking the packaging yesterday (which I didn't follow the reasoning behind, but ended up basing the beta2 packaging branch on an existing xnox branch) lost the Build- Depends we had on archive golang packages. What we had:

[Bug 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't > carried this forward. Is this expected (not described in changelog)? Perhaps > it > is because of --disable-scripting but I'm not sure. Indeed. We have always built juju-mongodb without the javascript engine because

[Bug 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't > carried this forward. Is this expected (not described in changelog)? Perhaps > it > is because of --disable-scripting but I'm not sure. Indeed. We have always built juju-mongodb without the javascript engine because

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

"Are you saying you want to use the embedded code copy? Has anyone looked at the testsuite issue to fix it? Embedded code copies should be avoided at all costs per MIR guidelines -- we are making huge concessions for the juju and lxd teams already, can someone take a look at this ftbfs and report

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

"Are you saying you want to use the embedded code copy? Has anyone looked at the testsuite issue to fix it? Embedded code copies should be avoided at all costs per MIR guidelines -- we are making huge concessions for the juju and lxd teams already, can someone take a look at this ftbfs and report

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

> * golang-go.crypto > - needs a bug subscriber Looks like it's ~ubuntu-server now. > * golang-gocheck > - can be dropped when bug #1504821 is fixed (comment #82) > * golang-goyaml > - can be dropped when bug #1504821 is fixed (comment #82) To clarify, I am making these changes on master.

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

> * golang-go.crypto > - needs a bug subscriber Looks like it's ~ubuntu-server now. > * golang-gocheck > - can be dropped when bug #1504821 is fixed (comment #82) > * golang-goyaml > - can be dropped when bug #1504821 is fixed (comment #82) To clarify, I am making these changes on master.

[Bug 1498655] Re: Steam Controller support: need read-write access to Valve-owned input event device nodes.

** Branch linked: lp:~gz/ubuntu/wily/steam/new_rel_udev_rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498655 Title: Steam Controller support: need read-write access to Valve-owned input

[Bug 1498658] Re: Steam Controller support: need read-write access to /dev/uinput for controller emulation

** Branch linked: lp:~gz/ubuntu/wily/steam/new_rel_udev_rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498658 Title: Steam Controller support: need read-write access to /dev/uinput for

[Bug 1500981] Re: juju-db segfault while syncing with replicas

This package hasn't changed in trusty in more than a year.

[Bug 1500981] Re: juju-db segfault while syncing with replicas

This package hasn't changed in trusty in more than a year.

[Bug 1494441] Re: ppc64el: cannot find package "encoding"

This has been temporarily addressed on master by backing out the change responsible: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494441 Title: ppc64el:

[Bug 1029471] Re: Apport add_info hook should not add ppa version as tag

** Changed in: unity (Ubuntu) Status: In Progress = New ** Changed in: unity (Ubuntu) Assignee: Martin Packman (gz) = (unassigned) ** Changed in: unity Status: In Progress = New ** Changed in: unity Assignee: Martin Packman (gz) = (unassigned) -- You received this bug

[Bug 1330504] Re: strongSwan 5.1.3

** Project changed: strongswan = obsolete-junk ** No longer affects: obsolete-junk -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1330504 Title: strongSwan 5.1.3 To manage

[Bug 1330504] Re: strongSwan 5.1.3

** Project changed: strongswan = obsolete-junk ** No longer affects: obsolete-junk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330504 Title: strongSwan 5.1.3 To manage notifications about this

[Bug 1381671] Re: reboot tests fail to build on gccgo

Thanks Michael! I guess I'll need to be pretty conservative about removing the workaround in juju as we're testing on multiple ubuntu releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381671

[Bug 1393825] [NEW] Juju testsuite fails in random ways

Public bug reported: Two parts of the juju-core test suite panic or segfault when run with -compiler gccgo on amd64. Some examples, in provider/openstack: ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test ./... -compiler gccgo -gocheck.v -v) 3 === RUN Test ... PASS:

[Bug 1393825] [NEW] Juju testsuite fails in random ways

Public bug reported: Two parts of the juju-core test suite panic or segfault when run with -compiler gccgo on amd64. Some examples, in provider/openstack: ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test ./... -compiler gccgo -gocheck.v -v) 3 === RUN Test ... PASS:

[Bug 1393825] Re: Juju testsuite fails in random ways

** Description changed: Two parts of the juju-core test suite panic or segfault when run with -compiler gccgo on amd64. Some examples, in provider/openstack: ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test ./... -compiler gccgo -gocheck.v -v) 3 === RUN

[Bug 1393825] Re: Juju testsuite fails in random ways

The HTTPS side of this I can reproduce (inconsistently) running just one test: ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test ./... -compiler gccgo -v -gocheck.v -gocheck.f=TestMustDisableSSLVerify) 3 === RUN Test unexpected fault address 0x7f6b0011 fatal error:

[Bug 1393825] Re: Juju testsuite fails in random ways

Another part of this is from a panic in a later test: ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test ./... -compiler gccgo -v -gocheck.v -gocheck.f=TestStartInstanceWithUnknownAZError) 3 === RUN Test

[Bug 1381671] Re: reboot tests fail to build on gccgo

Status: Triaged = In Progress ** Changed in: juju-core Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title

[Bug 1381671] Re: reboot tests fail to build on gccgo

** 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 gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title: reboot tests fail to build on gccgo To manage

[Bug 1381671] Re: reboot tests fail to build on gccgo

Status: Triaged = In Progress ** Changed in: juju-core Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title: reboot tests fail

[Bug 1381671] Re: reboot tests fail to build on gccgo

** Changed in: juju-core 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/1381671 Title: reboot tests fail to build on gccgo To manage notifications about

[Bug 1381671] Re: reboot tests fail to build on gccgo

** 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/1381671 Title: reboot tests fail to build on gccgo To manage notifications about

[Bug 1248283] Re: juju userdata should not restart networking

** Changed in: juju-core Milestone: 1.20.0 = 1.18.0 -- 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/1248283 Title: juju userdata should not restart networking To manage

[Bug 1248283] Re: juju userdata should not restart networking

** Changed in: juju-core Milestone: 1.20.0 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: juju userdata should not restart networking To manage notifications about this

[Bug 1268913] Re: Loading state on bootstrap ignores ssl-hostname-verification setting

Now merged in Curtis, thanks. ** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: 1.18.0 = 1.17.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1261628] Re: remove-* aliases for destroy-service and destroy-machine

** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: 1.18.0 = 1.17.4 -- 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/1261628

[Bug 1268913] Re: Loading state on bootstrap ignores ssl-hostname-verification setting

Now merged in Curtis, thanks. ** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: 1.18.0 = 1.17.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1261628] Re: remove-* aliases for destroy-service and destroy-machine

** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: 1.18.0 = 1.17.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261628 Title: remove-*

  1   2   3   >