date:20160816

[Bug 1612550] onibi (i386) - tests ran: 136, failed: 0

2016-08-16 Thread Brad Figg

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76/onibi__3.19.0-68.76__2016-08-16_12-41-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612550

Title:
  linux: 3.19.0-68.76 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613718] [NEW] [SRU] Juju 2.0-beta15 for Xenial

2016-08-16 Thread Nicholas Skaggs

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, including for major version
updates, https://wiki.ubuntu.com/JujuUpdates.

[Impact]
This update brings many critical fixes and enhancements in comparison to the 
current beta12 release.

A full list of targeted bugs can be seen against the milestone, and the
intervening milestones:

https://launchpad.net/juju-core/+milestone/2.0-beta13
https://launchpad.net/juju-core/+milestone/2.0-beta14
https://launchpad.net/juju-core/+milestone/2.0-beta15

[QA/Testing]
Juju practices continuous integration and testing of the juju source tree. The 
results for this release can be seen here.

http://reports.vapour.ws/releases/4233

In addition, juju has adt test coverage for all supported archs,
http://autopkgtest.ubuntu.com/packages/j/juju-core/.

Finally, manual verification and testing of the package has been done
per https://wiki.ubuntu.com/JujuUpdates

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

** 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 stable release exception, including for major version
  updates, https://wiki.ubuntu.com/JujuUpdates.
  
  [Impact]
  This update brings many critical fixes and enhancements in comparison to the 
current beta12 release.
  
  A full list of targeted bugs can be seen against the milestone, and the
  intervening milestones:
  
  https://launchpad.net/juju-core/+milestone/2.0-beta13
  https://launchpad.net/juju-core/+milestone/2.0-beta14
  https://launchpad.net/juju-core/+milestone/2.0-beta15
  
  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here.
  
- http://reports.vapour.ws/releases/4242
+ http://reports.vapour.ws/releases/4233
  
  In addition, juju has adt test coverage for all supported archs,
  http://autopkgtest.ubuntu.com/packages/j/juju-core/.
  
  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613718

Title:
  [SRU] Juju 2.0-beta15 for Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1613718/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1612895] Re: Display freezes on 2nd+subsequent logins

2016-08-16 Thread Nathan Dorfman

Thanks for the suggestion. Unfortunately, it's at least as bad with the
new kernel; maybe worse.

So first of all, "2nd login" doesn't reproduce the issue 100% reliably
after all. I tested one last time with kernel 4.4.0-31, and the same
exact problem occurred again, but on the 3rd, not 2nd login. I then
rebooted into the new kernel 4.8.0-040800rc2, and was able to reproduce
it, but it was after the 3rd *logout.* The machine froze on the black
console screen that normally appears just momentarily after the desktop
goes away but before the lightdm login screen reappears.

After eventually regaining control, I logged in again and the display
froze shortly before the desktop was completely drawn, more or less as
expected. Unfortunately, this time Ctrl+Alt+F1 had no effect after any
length of time. Having neglected to first install sshd, I had to hard
reset the machine after 30 minutes or so of waiting. I haven't had that
happen with the old kernel, but that could also just be luck.

By the way, is it possible this bug should be against Xorg instead? The
kernel version on my 14.04 installation is 4.4.0-34, or pretty close to
the 4.4.0-31 kernel I'm having issues with.

< 2 3 4 5 6 7 8 9 >

601 - 700 of 861 matches

Mail list logo