# reusing the path in gdb
set env LD_LIBRARY_PATH /root/newertls/usr/lib/x86_64-linux-gnu/
# that brought me to wonder that in the bad case the following break did not
catch anything
b virNetTLSContextCheckCertDN if strcmp(dname, "C=UK,CN=libvirt") == 0
# I realized that they were different
Public bug reported:
Trying to use sbuild to build packages in an lxd container and it won't
build and displays an error:
$ mk-sbuild zesty
mknod: /var/lib/schroot/chroots/zesty-amd64/test-dev-null: Operation not
permitted
E: Cannot install into target '/var/lib/schroot/chroots/zesty-amd64'
*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300
BTW this is still present in 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/830348
Title:
desktop
*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300
Also occurs when suspending by closing the lid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/830348
Title:
Also in my case I solved it by disabling WMM, not sure how to solve this
for this ticket... Since it's really environment related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575321
Title:
thanks to you!
sorry for the long wait for this fix, but I always hope about a new
upstream release, and kernel breaks various times in RC releases, so it
would require a lot of uploads probably useless for most people (and
time consuming)
G.
--
You received this bug notification because you
@penalvch I guess better times are around the corner "Cypress just
bought Broadcom's wifi business and published all their datasheets
https://news.ycombinator.com/item?id=12965348;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(I also tried a firmware upgrade for the storage controller to the
latest version - no luck).
** Tags added: kernel-bug-exists-upstream-4.9-rc5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641593
** Also affects: snapcraft
Importance: Undecided
Status: New
** No longer affects: snapcraft (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642041
Title:
LD_LIBRARY_PATH values
I'am on 16.10 and it is still here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/390989
Title:
[SecurityRoadmap] Locked screen shows the desktop
To manage notifications about this bug go
I have exactly the same problem on Ubuntu 16.04. I have created a vpn
connection and it disconnects after almost 5 minutes. One weird thing is
that the laptop fan starts working with a high speed and exactly at the
same moment the vpn disconnects.
--
You received this bug notification because
When I "watch" a black video in VLC on the AOD255E or the bug-affected
Thinkpad, take a screenshot of thath blackness and display the image
file in eog, I see what I'd expect to have seen in the video at that
position.
--
You received this bug notification because you are a member of Ubuntu
Just bought an APC Back-UPS 350VA 230V (BK350EI) and after struggling for a
couple of days find these posts on your forum. At first I had no monito on the
server, which is now set. Everything goes so quickly that I cannot give any
information. I see nothing of the script /etc/init-d/ups-monitor
I've installed latest mainline build and awaits the issue... I have
definitely seen the issue with the 4.9-rc4 mainline build, but the rc5
just yet... I'll be back with an update in a few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The upgrade is fine (source not installed, as usual).
Thanks LOB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642163
Title:
virtualbox-dkms 5.1.8-dfsg-6build1: virtualbox kernel module failed to
OK tried with:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5/
still see the same issue with intel_iommu=on; booted fine prior to
enabling.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
nvidia 340.98 is failed with kernel 4.9.x
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nvidia-340 340.98-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
In case it helps: On the AOD255E, lspci | grep VGA | cut -d : -sf 3-
Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics
Controller
On the AOD360:
Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics
Controller
(however, this one runs on Ubuntu
Public bug reported:
package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
install/upgrade: el subproceso instalado el script post-installation
devolvió el código de salida de error 1
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: url-dispatcher:amd64
Hi Joseph
The problem happens both during install, and during a regular boot (for
example if I enable iommu post install and then reboot).
Happy to try new kernel versions for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same problem on xenial in an Acer Aspire One 255 (AOD255E), also in VLC.
gnome-mplayer shows the video but at a very slow frame rate, and in
cases where it has to scale the image up to make it fill the screen, the
image quality is worse than on an Acer Aspire One 360 with VLC (same
resolution,
FYI - reported the lack of an FTBFS in Debian as debbug 844511
Not linking this bug here as it is not about "this" issue, but the question why
it wasn't an FTBFS for Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug affects me on Ubuntu 16.04, only that now it is thunderbird
instead of evolution. The mail indicator applet changes its color only
very third or fourth time new mail arrives. I have no clue as to why it
only sometimes reacts, I have only one mail account.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gstreamer0.10 (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/661735
@acarbura yes it does
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566302
Title:
Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
4.4.0-16
To manage notifications about
Taking Yakkety and Zesty being one with and one without the new gnutls.
# Try most basic build as reasonable for debug and a report upstream
$ apt-get install -y ubuntu-dev-tools gdb
$ apt-get -y build-dep libvirt
$ git clone git://libvirt.org/libvirt.git
$ cd libvirt
$ export CFLAGS="-g -O0"
$
Thats kernel 4.4.07.68
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrade to
16.04
To manage notifications about this
Public bug reported:
== Comment: #0 - Breno Henrique Leitao - 2016-10-20
08:51:24 ==
Hello Canonical,
There are important kernel modules that are required on POWER systems,
and they are currently on the linux-image-extra packages.
So, in this case, every Power system needs
Got the same problem with Logitech RX250 on Xubuntu 16.04.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581088
Title:
Middle mouse (wheel-click) button stopped working after upgrade to
16.04
> There was a lot of extra mirroring on this - another bugproxy issue?
Probably. Apologies for you getting that. Please disregard it. :/
> Also while I know the maintainer scripts already have the same issue
> I today accidentally came by this
>
PS: Uninstalling the installer also removed the fonts from
/usr/share/fonts/truetype/msttcorefonts , so make backup
before you uninstall it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641671
I don't think so, this is just snapd itself growing as it eats up heap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642068
Title:
snapd memory sizes grows huge over time
To manage notifications
I tried to debug it, but the coding style of /usr/lib/msttcorefonts
/update-ms-fonts lead me to decide I'll rather uninstall the ttf-
mscorefonts-installer after initial system setup. I'll uninstall it now
and expect the mail messages will end then.
--
You received this bug notification because
DimanNe
See https://workingninja.com/installing-asus-bt400-raspberry-pi-raspbian-wheezy
It will show how to get the firmware needed for the broadcom bluetooth device
and see if the issue still exists after the firmware install
--
You received this bug notification because you are a member of
could this be related to Bug 1636847 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642068
Title:
snapd memory sizes grows huge over time
To manage notifications about this bug go to:
While the workaround is being prepared to get SRUed to the stable
releases, I prepared the dbus packages with the two patches Simon
proposed for testing.
https://launchpad.net/~sil2100/+archive/ubuntu/ppa
Could anyone that was able to reproduce the original issue install the
dbus packages from
Or even better:
If lxd is configured to use zfs, then it should do what it is configured
to do, and not try to be wiser that its admin. It then should wait for
the zfs to appear before doing anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: msttcorefonts (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/1641671
My output after starting the update from shell was:
update-manager
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
from gi.repository import Gtk
Hi, all resolved, it was due to a faulty micro usb cable. Sorry about all the
trouble and thanks.
Koli
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641075
Title:
connected my android phone, htc
Hi
I've worked out I had a problem with micro usb cable. Ive replaced the cables
and it is working fine now. sorry about all the trouble. Thanks Koli
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
missing
QT_IM_MODULE=gcin
in /usr/share/im-config/data/26_gcin.rc
QT5 needs this.
+
+ Fix uploaded to yakkety queue; xenial patch attached to bug #1642001.
[Test Case]
After the change, this command:
grep -A3 QT_IM_MODULE
I've experienced same problem. I assume problem is with some PPA
applications running in python.
I tried @Lubos solution, but result was still same. I've noticed that after
init 2 there was still running some proceses of my-weather-indicator. (PPA
https://launchpad.net/my-weather-indicator ).
Public bug reported:
STEPS:
Prerequisite:
A system with UEFI and Secureboot enabled
1. Install Zesty image from a couple of days ago
2. Update the system and run top
EXPECTED:
I expect the system to update and close
ACTUAL:
System stops late on in the upgrade process and triggers 100% of cpu
pwaring I think fix-committed state means that a patch has been committed to
ubuntu repository, then automatic test are run on it and qa, et all, if there
are no regression it will be released.
If things goes bad then a new patch should be committed, and so. (I guess it
works something like
** Summary changed:
- Yakkety version of transcode needed (removal causes unmet depdendencies)
+ Yakkety version of transcode needed (removal causes unmet dependencies)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
after init is done and vars can be checked
b virnettlssessiontest.c:95
Then it initializes server and client context without checks intentionally
to detect problems via the TLS session validation stage.
virNetTLSContextNewServer
virNetTLSContextNewClient
Both work (wildcard is used on Server
** Description changed:
[Impact]
XIM support check for Qt5 in UIM is broken — it uses the same paths as
for Qt4, but they've been changed.
+
+ Fix uploaded to yakkety queue; xenial patch attached.
[Test Case]
After the change, this command:
grep platforminputcontexts
Bug still present in Ubuntu 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/977228
Title:
gnome-screenshot forgets "last-save-directory"
To manage notifications about this bug go to:
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642192
Title:
i386 4.9 in -proposed fails to boot in cloud instances
To manage
Add audit=0 to kernel command line and logd ceases to try kernel audit,
and the rest of the system (lxd/snap) doesn't seem to be affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
AppArmor is not functioning this way Hmmm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage notifications about this bug go to:
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
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
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
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
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
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
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
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
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
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
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
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
Neither gnutls upgrade announce to change anything around this:
https://lists.gnupg.org/pipermail/gnutls-devel/2016-October/008194.html
https://lists.gnupg.org/pipermail/gnutls-devel/2016-November/008221.html
Interestingly the tests are the follwing way:
expect-srvfail expect-clientfail result
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
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
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
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
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
@dino99, yesterday linux4.9 reached zesty, so I'll fix it in a few
seconds
** Changed in: virtualbox (Ubuntu)
Status: Invalid => New
** Changed in: virtualbox (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
501 - 600 of 656 matches
Mail list logo