Dann - https://lists.ubuntu.com/archives/kernel-
team/2016-October/080408.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634585
Title:
[REGRESSION] rtc-efi no longer statically linked on arm64
Will we see this fix make it to 16.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518457
Title:
kswapd0 100% CPU usage
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1585737/+attachment/4763376/+files/shot-20160525194720.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Nope. It's more like the other way around.
I clicked on a window (opened by an application) but it shot only the
application main window rectangle, even if it was partially covered. See
attached screenshot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "the_samba_install_log"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1629038/+attachment/4763373/+files/samba_errors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-44.64/onza__4.4.0-44.64__2016-10-18_17-45-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/1633414
Title:
linu
+1 having same issue where light remains flashing after i login using
the finger print or via keyboard entered password. Work around is to
pass the finger over it once again to stops it.
thanks
P.S kernel: 4.7.7-200
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I confirm that installing postgresql-9.6 still produces multiple
messages on a freshly updated 16.04 server instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538284
Title:
Unescaped left brac
** No longer affects: ubuntu-image (Ubuntu Yakkety)
** No longer affects: ubuntu-image (Ubuntu Zesty)
** No longer affects: ubuntu-image (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632134
** No longer affects: ubuntu-image (Ubuntu Zesty)
** No longer affects: ubuntu-image (Ubuntu Yakkety)
** No longer affects: ubuntu-image (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631961
** Description changed:
- Probably relates to #1612517
+ Probably relates to
+ https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517
Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial).
I'm not sure from which version the config originates. After the option
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Trusty)
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
** No longer affects: ubuntu-image (Ubuntu)
** No longer affects: ubuntu-image (Ubuntu Yakkety)
** No longer affects: ubuntu-image (Ubuntu Zesty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632085
With libqt5core5a 5.5.1+dfsg-16ubuntu7.2 I have no problem for the
Asia/Novosibirsk timezone.
Sorry for delay. I faced another bug that I did not noticed just after upgrade
to 16.04.
Now I see that missing cities such as Europe/Astrakhan or Asia/Barnaul in
digital clock
settings are unrelated to
I can confirm this on Ubuntu 16.04 running GNOME Shell, the fix from #4
works though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514163
Title:
transgui instantly crashes on start
To manage noti
ubuntu@ubuntu:~$ archdetect
arm64/efi
ubuntu@ubuntu:~$ cat /proc/version
Linux version 3.13.0-99-generic (buildd@bos01-arm64-032) (gcc version 4.8.4
(Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.3) ) #146-Ubuntu SMP Wed Oct 12 20:56:37
UTC 2016
** Tags removed: verification-needed-trusty
** Tags added:
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-43.63/s2lp3__4.4.0-43.63__2016-10-18_17-18-00/results-index.html
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New =>
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-43.63/s2lp6g001__4.4.0-43.63__2016-10-18_17-18-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/1633414
Title:
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-43.63/kernel01__4.4.0-43.63__2016-10-18_17-18-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/1633414
Title:
** Changed in: kernel-sru-workflow/security-signoff
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/1633419
Title:
linux-raspi2: 4.4.0-1028.34 -proposed tracker
To man
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Released
** Changed in: kernel-sr
** Package changed: ubuntu => apcupsd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634572
Title:
APCUPSD does not send killpower command to UPS (only happens on Ubuntu
16.04)
To manage
Public bug reported:
The current kernel in trusty-proposed has changed rtc-efi to a module on
arm64:
ubuntu@ubuntu:~$ grep RTC_DRV_EFI /boot/config-3.13.0-9*
/boot/config-3.13.0-98-generic:CONFIG_RTC_DRV_EFI=y
/boot/config-3.13.0-99-generic:CONFIG_RTC_DRV_EFI=m
This breaks setting the clock on b
** Package changed: ubuntu => cloud-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634543
Title:
yakkety-server-cloudimg-amd64-root.tar.gz to create LXD containers not
available
To manage
This issue was fixed in the openstack/nova 14.0.0.0rc1 release
candidate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608934
Title:
ephemeral/swap disk creation fails for local storage with image
--- Comment From ha...@us.ibm.com 2016-10-18 12:53 EDT---
Same host hung again under similar workload.
Will attach kernel log from new hang as "dlfire5-oct18b-kern.log".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
--- Comment (attachment only) From ha...@us.ibm.com 2016-10-18 12:55
EDT---
** Attachment added: "host 'dlfire5' hang from morning of Oct 18th (2nd hang)"
https://bugs.launchpad.net/bugs/1633223/+attachment/4763344/+files/dlfire5-oct18b-kern.log
--
You received this bug notificatio
Thanks for responding. :)
Indeed, subtitleripper lists transcode as a dependency [1]. It is
currently not installable on Ubuntu 16.10 since transcode is missing.
Odd, because I thought reverse dependencies were checked or would block
package removal...
[1] http://packages.ubuntu.com/yakkety/subt
Public bug reported:
Probably relates to #1612517
Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial).
I'm not sure from which version the config originates. After the option to send
this report, I also saw this message in the terminal:
Setting up mysql-server-5.7 (5.7.1
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566221
Title:
linux: Enforce signed module loading when UEFI secure boot
To manage notifications about this bug go to:
This issue was fixed in the openstack/cinder 9.0.0.0rc1 release
candidate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619246
Title:
Capacity filter and weigher fails when volume has no volume ty
This issue was fixed in the openstack/ceilometer 7.0.0.0rc2 release
candidate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624873
Title:
ceilometer-api failed to start
To manage notifications ab
Hi,
As a fix for problems in 16.04, I had a grub option in my
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=0"
After removing this option I can now set my brightness and the
resolution of the screen
NOW:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
--
You received this
according to our IRC talk it seems that clearing out the old libs got it
resolved on the second try.
Yet it all feels a bit messy as:
- it didn't work on the first try
- we still don't know how it happened to be around in the first place
Yet I'd like to invite all reporters of duplicate bugs to t
I believe we are running into the same bug on 4.4.0-34-generic. Here is
the output of dmesg when the issue starts. Let me know if I can provide
any more info.
INFO: task kworker/1:1:20481 blocked for more than 120 seconds.
Not tainted 4.4.0-34-generic #53~14.04.1-Ubuntu
"echo 0 > /proc/sys/k
** Changed in: ubuntu-docs (Ubuntu)
Assignee: (unassigned) => Chris Perry (clissold345)
** Changed in: ubuntu-docs (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
*** This bug is a duplicate of bug 1634528 ***
https://bugs.launchpad.net/bugs/1634528
** This bug has been marked a duplicate of bug 1634528
16.10 compiz assert failure : double free or corruption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Project changed: elementaryos => switchboard-plug-about
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633161
Title:
1.79gb ram detected, 8gb ram installed
To manage notifications about this bug
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634575
Title:
package libc6-i386 2.23-0ubuntu3 failed to install/upgrade: package
libc6-i386 is already install
Public bug reported:
This happens for every command and is nothing a user can fix:
# openstack --version
WARNING: openstackclient.common.utils is deprecated and will be removed after
Jun 2017. Please use osc_lib.utils
openstack 3.2.0
# apt policy python-openstackclient
python-openstackclient:
Thanks Christian, I'll give uvtool a try.
On 2016-10-18 11:56 AM, ChristianEhrhardt wrote:
> Thanks Matt for your reply.
> AFAIK that is what smb already tried in comment #4.
My hosts were fresh installs but the guests xml were carried from an
older version.
> Never the less I checked the upgrad
Happened again from 16.04 to 16.04.1
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511459
Title:
interface p1p1 renamed to eth0 after upgrade from 15.04 to 15.10
To manage n
Public bug reported:
Trying to install nvidia drivers update to two external monitors
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libc6-i386 2.23-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Ap
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Released
** Changed in: kernel-sr
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ufw (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/1631553
Title:
With U
** Tags removed: bugnameltc-146511 kernel-4.8 severity-critical
verification-needed-trusty verification-needed-xenial verification-
needed-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628976
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Summary changed:
- sound and video doesn't work with rocket.chat
+ [webbrowser] sound and video doesn't work with rocket.chat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634549
Title:
[webbro
I know this is not the most world-shattering bug, but any chance we
could see a fix for this?
primes still (in 2016!) shows composites, which can be seen by doing:
=$ primes 35198908481059600 35198908481059602
35198908481059601
=$ factor 35198908481059601
35198908481059601: 181399 405277 478787
** Tags removed: verification-needed-trusty
** Tags added: verification-done-xenial
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566221
Title:
linux: Enfor
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
Public bug reported:
I have spoken to users on the apcupsd mailing list and they seem to
think this is a bug on Ubuntu 16.04.
as the title states, since i installed a fresh copy of Ubuntu 16.04, and
compiled the latest version of apcupsd 3.14.14 source, when PC shuts down,
killpower is not bein
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
G'day Brad,
I tried that and got an error message telling me I have to get and
install 'python-apport' before it can be run. That being the case I'm
not sure any logs from it will be of use. 1. Because it wasn't logging
when the issue happened, and 2. because the problem was occurring before
Kubun
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
Thanks Pavlusshka for the try to clean and update.
But I doubt that the cleaning was complete for two reasons.
In http://paste.ubuntu.com/23344195/ line 7&8 it only reports the 64bit lib
would be around.
But in line 10-12 dpkg misses /usr/lib/i386-linux-gnu/libndr.so.0 - why is that?
On http://p
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
Package updates have been uploaded to zesty, yakkety, and xenial review
queues. Note: policy.json did not exist in mistral 2.0.0 (xenial).
Also contributed patch back to Debian:
https://review.openstack.org/#/c/388083/
--
You received this bug notification because you are a member of Ubuntu
Bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: motion (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/1372072
Title:
mot
Thanks Matt for your reply.
AFAIK that is what smb already tried in comment #4.
Never the less I checked the upgrade path once more.
With a modified conffile (just an empty line, but to not get the new one as in
the bug report here)
And with an old guest created on Xenial.
It was not triggering t
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633172
Title:
Linux 4.8 as in 16.10 hangs during boot
To manage notifications about this bug
** Tags removed: kernel-key
** Tags added: kerne-dal-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633267
Title:
Wifi and sound no longer detected in kernel 4.4.0-43
To manage notifications ab
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633391
Title:
Ubuntu doesn't boot anymore {REGRESSION}
To manage notifications about this bug
** Also affects: mistral (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => In Progress
** Changed in: mistral (Ubuntu)
Status: New => In Progress
** Cha
Public bug reported:
The "konsole" application seems to be in very bad shape in yakkety.
Possibly, this is not due to the konsole itself but the
qt/plasma5/plasma framework combination. Unfortunately, plasma 5 does
not seem to be able to stabilize.
To reproduce:
from a terminal type in "konsole"
** Patch added: "Xenial Patch for 1584485"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/+attachment/4763313/+files/fix-1584485-xenial.debdiff
** Patch removed: "trusty_samba_4.3.9+dfsg-0ubuntu0.14.04.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/+a
301 - 400 of 793 matches
Mail list logo
