** Changed in: linux-raspi2 (Ubuntu Xenial)
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/1737519
Title:
linux-raspi2: 4.4.0-1080.88 -proposed tracker
To manage
** Also affects: linux-azure-edge (Ubuntu Xenial)
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/1737597
Title:
linux-azure-edge: 4.14.0-1001.1 -proposed
** Also affects: linux-gke (Ubuntu Xenial)
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/1737824
Title:
linux-gke: 4.4.0-1035.35 -proposed tracker
To
** Changed in: linux-aws (Ubuntu Xenial)
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/1737515
Title:
linux-aws: 4.4.0-1044.53 -proposed tracker
To manage
** Changed in: linux-aws (Ubuntu Trusty)
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/1737512
Title:
linux-aws: 4.4.0-1006.6 -proposed tracker
To manage
qemu-guest-agent and pm-utils are both universe so adding a dependency or
better a recommends as that is what it correctly is is an option if that turns
out to help.
Independent to a fix of this issue (which we don't know yet if it is one) it
would also ensure that anything that plug into
Dear users,
We are treating this issue very seriously and sorry that this has
happened. We have been working with Lenovo in China at full speed since
last week to find out the root cause. Meanwhile, if you hit this issue,
please send me an email at anthony.w...@canonical.com with your laptop's
Hi,
should I un-comment it?
-rw-rw-r-- 1 root root 1218 nov 28 2016 /etc/fstab
2017-12-13 8:52 GMT+01:00 Steve Langasek :
> Ok, so the problem is that your /boot/efi entry is commented out.
>
> On Wed, Dec 13, 2017 at 07:28:17AM -, Michele Polese wrote:
> > #
Public bug reported:
== SRU Justification ==
[Impact]
Some QCA ROME bluetooth devices does not work after runtime suspended.
[Fix]
Latest mainline does not have this issue. The bisected commit is
a0085f2510e8976614ad8f766b209448b385492f "Bluetooth: btusb: driver to enable
the usb-wakeup
** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu)
** Summary changed:
- gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts
** Tags removed: vivid
** Tags added: bionic xenial
@John I fully agree. All this information is already available to juju,
so IMHO juju should just use it. Instead of picking up information from
MAAS, juju should just take a peak into host's cloud-config data and use
it to generate LXD and KVM cloud-config. Obviously, it should override
some
Public bug reported:
[Impact]
A change was landed in dell-wmi.ko which extend scan code of microphone mute
from 0x150 to 0x100150, so that we need to add the mapping as well.
related commit:
https://github.com/systemd/systemd/pull/5012
also affects:
LP: #1736352
[Test Case]
1. install the new
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
** Affects:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workflow
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: 1737913
derivatives:
**
> I'm already of why the prebuilt ones were removed,
great
> but that doesnt't
> actually answer how they were missed when updating qemu to 2.7 (vmxnet3
> PXE is mentioned in the changelog).
Updating qemu is distinct from updating ipxe.
So when we moved what was I think qemu 2.6.1 -> 2.8 that
Hi Tobias,
Thanks for this bug/follow-up.
The latest glances version was imported inside Debian :)
Cheers,
** Changed in: glances (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
This change was made by a bot.
** Changed in: linux (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/1737934
Title:
Samsung SM961 NVMe SSD randomly
Even better, you could try to test latest master of LyX, where a new
screen painting strategy has been implemented. This may eventually be
backported to the 2.3 series at a later time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I cannot reproduce this bug wih LyX 2.2.3. Does anyone still see it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/560715
Title:
When I try to insert Floating Image, lyx crashes with message "lyx:
--- Comment From nikunj.dadha...@in.ibm.com 2017-12-13 06:03 EDT---
Patches commited:
https://github.com/aik/SLOF/commit/1e8f6e68d28132e70898bd4bd6f799b591c3bf2b
https://github.com/aik/SLOF/commit/80f74b855f2f67ae5ed45b0d32c57dce46585da7
Should reflect in qemu repository in a day
--
Not yet.
This is currently in the sponsorship queue, so for those not familiar
with the procedure, point 6 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure .
As you can see using "rmadison livecd-rootfs" another SRU for livecd-
rootfs is under way (for something unrelated to this bug),
*** This bug is a duplicate of bug 1438014 ***
https://bugs.launchpad.net/bugs/1438014
Surprise, it's been affecting gnome-terminal for years: bug 1438014.
** This bug has been marked a duplicate of bug 1438014
gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
--
i dont believe so,
i had to uninstall WSL and reinstall it
from an admin command prompt i ran
`lxrun /uninstall /full`
then
`lxrun /install`
or, if you want the default user to be root without a password
`lxrun /install /y`
--
You received this bug notification because you are a member of
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-phase:Packaging
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow
This needs fixing in the systemd units for ovs; raising packaging tasks.
** Also affects: openvswitch (Ubuntu)
Importance: Undecided
Status: New
** Changed in: openvswitch (Ubuntu)
Status: New => Triaged
** Changed in: openvswitch (Ubuntu)
Milestone: None => ubuntu-18.04
This change was made by a bot.
** Changed in: linux (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/1731041
Title:
kernel
To manage notifications about this
Please note that we are re-spinning Xenial kernels to release a fix for
this issue faster, so the dates from comment #25 don't apply for this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737033
Sorry - found some other qemu-guest-agent issues along that were easier to
address and I did so right away.
Back on this now.
The actions run by the guest-agent are:
- guest-sync (this is only to ensure no old content is on the channel, no
relation to suspend)
- guest-suspend-ram (the actual
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of update-initramfs that you likely have
installed is unable to work on a persistent usb stick. You can resolve
this issue by upgrading the version of casper on your system. This can
be done via the
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ backports:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hi @Łukasz,
I tried to run the acc test manually, and it didn't show any error.
The environment I used is vagrant + xenial/amd64 image (not fully upgrade all
of the packages) + ppa mentioned in #18 + related packages/tools.
May I have your opinion what could be the differences?
I also did
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ backports:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
(late) Hi,
You are right Laurent, IMHO they should be added.
Not very critical since as of today there are no conffiles in there yet, but
still right to do so.
Adding an Ubutu task to include the fix and actually also the script to
better support the freeze/thaw operations.
** Also affects:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Do you still suffer from this bug? I have never seen something like
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636580
Title:
Lyx UI fonts are all "italic" and do not display correctly
To
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ backports:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Taking a look.
** Changed in: samba4 (Ubuntu)
Status: Incomplete => New
** Changed in: samba4 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690502
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680268
Title:
Same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 opened one
year earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690502
Title:
ACPI Error:
It's likely that this was either fixed upstream or the root cause is
from a patch that was put on the 4.13 kernels that the 4.14 kernels
don't have.
Nov 05 22:15:30 lakshmi kernel: Linux version 4.13.0-16-generic
(buildd@lcy01-02) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP
Wed
Public bug reported:
16.4ubuntu failed in reestart config.
i shut build again?
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic i686
ApportVersion:
More log output from ovs:
2017-12-13T12:40:23.502Z|5|dpif(revalidator20)|WARN|system@ovs-system:
failed to put[modify] (Invalid argument)
ufid:684991e8-860e-44eb-ab44-bd8bd41520e1
root 16037 1 0 12:39 ?00:00:00 ovsdb-server: monitoring pid
16038 (healthy)
root 16038 16037 0 12:39 ?00:00:00 ovsdb-server
/etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info
--remote=punix:/var/run/openvswitch/db.sock --private-key=db:Open_vSwitch
I can confirm this behavior in xenial, but to be honest I'm not sure
what's the correct expected outcome.
Can you perhaps accomplish something similar using /usr/sbin/policy-
rc.d? You can create that script and it would check if samba is the
service being started, and then check if the disk you
>From our analysis, we indeed agree with the fact that it has nothing to do
>with LXC (hence the report in the systemd tracker).
We believe that only the package is faulty here and should not attempt to
blindly reexec systemd on upgrade.
--
You received this bug notification because you are a
@Nikunj - do you happen to know if Alexey is planning an official
release soon that would include this fix?
Note: this is the first Delta to take, but I look into it as it is critical.
We want to get back to have upstream release a version, debian pick it up and
we become a sync again in
** Changed in: gdesklets (Debian)
Status: New => 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/83922
Title:
gdesklets does not start
To manage notifications about this bug go
** 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/1737986
Title:
package libpcrecpp0v5:amd64 2:8.38-3.1 failed to install/upgrade:
package libpcrecpp0v5:amd64 is
Public bug reported:
Error
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpcrecpp0v5:amd64 2:8.38-3.1
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Not anymore. Something to do with the toolkit UI and me using
mate-desktop and something in the toolkit UI settings I think was
causing the issue.
On 12/13/2017 05:41 AM, Jean-Marc Lasgouttes wrote:
> Do you still suffer from this bug? I have never seen something like
> that.
>
--
You
** Summary changed:
- linux-hwe: -proposed tracker
+ linux-hwe: 4.10.0-43.47~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Description changed:
[Impact]
As part of allowing Ubuntu users to enable canonical-livepatch from
software-properties GUI
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite
few
This looks promising
https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html#interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737998
Title:
trying to bind on all interfaces is a good
** Summary changed:
- mount can exit (success) when it fails
+ mount can exit 0 (success) when it fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736556
Title:
mount can exit 0 (success) when
Public bug reported:
The default is "grab all" which is great for convenience and can be
configured to be differently by argument -I (interface) or interface
commands in the config.
Currently it is "too" open on that.
I see it trying to bing link local addresses for each of the KVM guests I
Either a restart after the package upgrade or nothing at all. But not a
'start' of Docker as it is was when I opened the bug. Don't know if that
has changed since, almost a year has passed by.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Install fails for systemd-shim, linux-image-4.10.0-42, linux-
image-4.10.0-42generic, linux-generic, virtualbox, virtualbox-qt,
initramts-tools.
I was able to boot with linux-4.4.4-040404-generic.
Now I cannot use VirtualBox and GNS3.
Regards.
ProblemType: Bug
I have extended the bug description to include the additional
information requested by @racb.
** Description changed:
[Impact]
The following issue was observed while running network-
manager=1.8.4-1ubuntu3 autopkgtest on Artful with
systemd=234-2ubuntu12.1:
Re: But the inner PV is only for the guest to use - no?
The intent is that the inner PV is only for the guest to use. What has
happened for years and years is that unless you mask using
/etc/lvm/lvm.conf the host will vgscan the inner PV and vgchange it too.
Until 17.10 (possibly 17.04, I
*** This bug is a duplicate of bug 1438014 ***
https://bugs.launchpad.net/bugs/1438014
Forgot to mention that 016_no_offscreen_widgets_grabbing.patch had never
been accepted upstream, as I learned in the discussion at
https://bugzilla.gnome.org/607668.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: android-platform-system-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (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/1695807
That being said, the linked samba bug is interesting:
https://bugzilla.samba.org/show_bug.cgi?id=13124
samba git master still has that change, i.e., use addr (ip) instead of
ldap_server_name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
That being said, the linked samba bug is interesting:
https://bugzilla.samba.org/show_bug.cgi?id=13124
samba git master still has that change, i.e., use addr (ip) instead of
ldap_server_name.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fix committed to bionic.
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug
13:30 infinity: missing SRU paperwork for bug 1730627, but also, do we
really need to SRU this? Is being able to debootstrap Bionic from Trusty
important?
13:30 bug 1730627 in dpkg (Ubuntu Trusty) "xz compressed control.tar
files not supported" [Medium,Confirmed]
Public bug reported:
Steps to reproduce problem:
_ Using python and matplotlib to plot something
_ When the plot appears, move the mouse to save icon
_ Boom, it's freezed
Wait several minutes for it to start moving again.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
I am running an environment (currently on Trusty) which supports
building packages for the current Ubuntu and Debian releases for a non-
trivial user group. For various reasons, I cannot update to Xenial in a
timely manner, and since Bionic is looming large, I want (and need) to
prepare for that
See also the screenshot here:
https://ubuntu-mate.community/t/huge-spideroak-icon-in-indicator-
applet/15036
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733301
Title:
indicator-applet-complete
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain
Public bug reported:
[Availability]
In universe
[Rationale]
New dependency for ceilometer (and aodh)
[Security]
No security history.
[Quality assurance]
py3: OK
unit tests during build: OK
[Dependencies]
All in main
[Standards compliance]
OK; debhelper9, python2&3
[Maintenance]
Bug subscription added for ubuntu-openstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737989
Title:
[MIR] ujson
To manage notifications about this bug go to:
Don't consider this as a bash bug. It's a misunderstanding by myself of
the pipeline operation.
Maybe a comment should be included in the reference manual to cleary
explain that the last command may try to open for writing the file still
open for reading by the first command, and that such a
py-macaroon-bakery cannot be imported as it is (otherwise we'll need to
update the version of protobuf and python3-nacl in xenial, breaking all
applications already using it). Please find attached the proposed
debdiff.
** Description changed:
[Impact]
As part of allowing Ubuntu users to
Hello NoOne, or anyone else affected,
Accepted libgweather into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgweather/3.24.1-0ubuntu0.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello NoOne, or anyone else affected,
Accepted libgweather into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.18.2-0ubuntu0.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello NoOne, or anyone else affected,
Accepted libgweather into artful-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu0.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
I don't have a data point for 4.11, but at 4.10 (as shipped in zesty)
ovs 2.8.1 tests are OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736390
Title:
openvswitch: kernel opps destroying
15:15 roaksoax: in bug 1732703, I'm not sure that test for systemd is
reliable. For example immediately after an upgrade from Trusty to Xenial,
before a reboot, /sbin/init will be systemd but the running init system will be
upstart.
15:15 bug 1732703 in MAAS 1.9 "MAAS does not detect properly
Now I've been watching more carefully, this does not just apply to the
file chooser window and the system monitor. It applies to many (all?)
dialogue windows with a multi-column internal layout, e.g. print.
Just now, the first time I tried to re-size the print window, it resized
itself glacially
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-2113
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576799
Title:
Regression: 2:4.3.8+dfsg-0ubuntu0.14.04.2 Failed to Issue the
I can see something similar from an ubuntu artful client if I force protocol
SMB3:
andreas@nsnx:~$ smbclient //10.0.100.215/ubuntu -U ubuntu%ubuntu -m SMB3
WARNING: The "syslog" option is deprecated
Domain=[XENIAL-SAMBA-SMBSTATUS-1737534] OS=[] Server=[]
smb: \>
server (xenial):
PID
I tried a few things more but not worth to mention - all dead ends.
Eventually I asked upstream if anybody ever achieved that and got no yes.
@Sean - given that this might have never worked so far and the package
being "only" universe did you ever see that succeed in a former version?
If not
101 - 200 of 671 matches
Mail list logo