*** This bug is a duplicate of bug 1755629 ***
https://bugs.launchpad.net/bugs/1755629
Hi Paul,
what you report seems correct to me but there is a very similar bug about this
where I'll dup this to to get a better overview on this.
** This bug has been marked a duplicate of bug 1755629
ep
Fix is known and seems backportable, marking as server-next and subscribing for
somebody to take a look.
Also as mentioned it is in 2.9, so newer releases are already fixed.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Stat
Thanks for the fast reply, David!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/288285
Title:
Using Calendar feature: Time errors
To manage notifications about this bug go to:
https://bugs.launchpa
I agree that LP#1626318 is essentially the same and dup'ed it onto this
one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755629
Title:
ephemeral-disk-warning yields /mnt 0444 immutable on package
** Bug watch added: Debian Bug tracker #870338
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870338
** Also affects: timidity (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870338
Importance: Unknown
Status: Unknown
** CVE added: https://cve.mitre.org/cgi-bin/c
I'd suggest to at least add something like
if [ -d "$(dirname $warn_file)" ]
around the cat
and then before the chmod/chattr
if [ -f "$warn_file" ]
This does not stop the current detection from being broken for multi
/bind-mounts, but should avoid at least some of the issues.
The file is not
** Package changed: linux-azure (Ubuntu) => null-and-void
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776284
Title:
@buy hydrocodone online +20
** Package changed: linux-azure (Ubuntu) => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
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 1670629 ***
https://bugs.launchpad.net/bugs/1670629
Hi Oliver,
this is a known issue that is being worked on, from your log:
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through
socket '/var/run/mysqld/mysqld.sock' (2) while connecting
I stopped using Thunderbird a few years ago. I cannot confirm whether
this is still an issue. This bug report should just be closed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/310021
Title:
c
Under the assumption of the auto-translate being:
The server lost and lost all the balance and the company asked for refund.
The company did not
answer anything, and I do not answer every time I try to contact them.
Is this company firm and deceptive?
I have to say that I can't help you at
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.
If you can provide exact steps so that a develope
TL;DR to get a newer version of postrgesql-client you need to update
your 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/1749585
Title:
postgresql-client-common is not compatible with
Hi Carlos.
Your system doesn't seems to have an apparmor mysql profile loaded
anymore. If it's a fresh ubuntu installation and you have only installed
mariadb, the precedent error is strange because we do not use apparmor
anymore (profile contains only comments).
> sudo apt-get remove --purge mys
Hi,
the version in Xenial is afaik only postgresql 9.5 (for the server and the
tools).
9.6 would be available in later releases like Ubuntu 17.10 and Ubuntu 18.04 is
already on postgresql-10.
I would not even see how you start to install postgresql-client-9.6 in
xenial without adding non support
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Public bug reported:
thanks in advance
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ub
No php7.1 in Bionic anymore - closing this old bug.
Whatever brought it back into proposed was resolved.
$ rma php7.1
php7.1 | 7.1.0-5 | unstable | source, all
php7.1 | 7.1.0-5 | unstable-debug | source
php7.1 | 7.1.16-1 | testing| source, all
php7.1
I don't know how your config change broke the configuration from the logs.
But that is what then breaks the update/reinstall.
For a service to be upgraded it needs to be restarted.
If you want to start from scratch you have to "apt remove --purge ..." which
will wipe any configuration. Otherwise
The X server ist not crashing, just halted.
After killing VLC, X is continuing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778402
Title:
VLC screen freeze
To manage notifications about this bug
That would imply it was resolved in slang2 (libslang2) 2.3.0-4 which is
in everything later than Xenial.
The change to consider for backporting would be
https://git.launchpad.net/ubuntu/+source/slang2/tree/debian/patches
/init-crash.patch?id=e633289c99ede705274a1b337a0deff5f8e08779
We should try
** Changed in: timidity (Debian)
Status: Unknown => 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/1443443
Title:
Arithmetic exception due to bad denom
To manage notifications ab
This was made available in Ubuntu Bionic (ethtool 4.15 along kernel
4.15).
Even thou there are HWE kernels that bring the newer Kernels to LTS releases
AFAIK there are no plans to also backport ethtool changes along that to ethtool
(which lives in the kernel teams scope now).
Subscribing Kerne
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Your logs indicate that your service is unable to start/restart due to local
configuration changes.
A fresh install starts just fine and the logs do not show a reason to assume it
is different.
On upgrading a se
Hi Gabor,
This sounds like, if the re-deployment is failing, curtin is not
correctly "cleaning" or allowing the reinstallation to work, even though
MAAS is sending the wipe: superblock option. I'm marking this as invalid
for MAAS, and opening a task for curtin.
** Also affects: curtin
Importan
Public bug reported:
this is my first in ubuntu system
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.18
Archite
Hi this looks like a broken config to me, from your logs:
[/etc/systemd/system/clamav-daemon.socket.d/extend.conf:4] Failed to parse
address value, ignoring: localhost:3310
clamav-daemon.socket: Unit lacks Listen setting. Refusing.
clamav-daemon.socket: Cannot add dependency job, ignoring: U
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Hi Christian,
as the server is a productive one I cannot just test to update to a dev-tagged
release...
So I'm really awaiting 18.04.01 to upgrade 16.04 to 18.04.
Best regards
Marc
> Christian Ehrhardt <1749...@bugs.launchpad.net> hat am 26. Juni 2018 um 14:11
> geschrieben:
>
>
> Hi,
> the
The GH issue calls this closed for 18.04 - setting the bug that way.
If there is more to do that I missed please update the bug accordingly.
** Changed in: walinuxagent (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs
The new versions are made available via the cloud-archive already on a regular
base.
We backport isolated fixed that have a low regression risk for other users, but
not sull versions per the SRU Policy
(https://wiki.ubuntu.com/StableReleaseUpdates).
Since it seems it was identified that the ver
Public bug reported:
Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu
18.04 (latest updates) guest.
Guest has 3 data disks apart from the boot disk. All these disks are exposed
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
Run diskio stress on all the 3 da
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1778717
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Attachment added: "screenshot-2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156771/+files/image-2018-06-22-14-48-57-801.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Attachment added: "screenshot-1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156770/+files/image-2018-06-25-10-13-05-871.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
The logs just have:
systemd[1]: tomcat8.service: Failed with result 'exit-code'.
But since a newly installed tomcat8 works there must be some setup/config
change that triggers that.
Without finding this - and at least to me I can't find it in the logs attache
so far - this bug can not really b
That fail to start then breaks the install/upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745193
Title:
package libvirt-daemon-system 3.6.0-1ubuntu6 failed to
install/upgrade: Unterprozess
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
>From your log:
Jan 24 19:08:23 hostname systemd[1]: virtlogd.socket: Socket service
virtlogd.service already active, refusing.
Jan 24 19:08:23 hostname systemd[1]: Failed to listen on Virtual machine log
manager socket.
Jan 24 19:08:23 hostname systemd[1]: Dependency failed for Virtual machine l
I have similar problem. I found the only way to set defaults for a new
input device (which also applies to Xorg re-adding the same devices at
some arbitrary times like suspend) at runtime, without restarting Xorg
to pick up modified xorg.conf, is to set xkb* udev properties on a
device (for example
Moving back to Confirmed state - since all the available logs are
already uploaded.
** 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/1
Thanks David, so it is a configuration detail when going into nested virt.
No change in qemu needed, setting tasks accordingly.
** Changed in: cloud-archive
Status: Incomplete => Invalid
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificati
* Also hit with 16.04.4 HWE kernel 4.13.0-45-generic.
* Not seen with LTS kernel 4.4 of Ubuntu 16.04
** Also affects: dellserver
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hi,
the own website [1] still calls it "should be considered a work in progress. As
such it is not a complete product nor should it be considered one. Extra care
should be taken when testing and configuring a system to use the KVMGT project".
That said I'm not sure what is expected here. I assum
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Hi,
I have to start with mentioning that libvirt-lxc really is deprecated and you
should consider using LXD for system containers - it is much better in
everything.
Further I took your definition and ran it on my system.
I switched the init call to bin/true (as I wanted to look at libvirt/host a
Public bug reported:
fresh install on a new machine
gigabyte h310m sh2
intel i3-8100
cannot "try without installing"
and the installer cannot install grub when installing.
the only mode i could install was the OEM install, and then boot from recovery
mode, and then choose resume, then i log in
** Description changed:
Availability
In sync with Debian.
Built for all supported architectures.
Rationale
=
Required for snaps.
Security
No known security issues, but due to the nature of this package, a security
review is probably neede
Needs more debugging why this triggers the GLIBC issues for the
reporter, setting incomplete until one has found time to debug it for
that.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
>From your log files:
/etc/ssh/sshd_config: line 91: Bad configuration option: Host
/etc/ssh/sshd_config: line 92: Bad configuration option: ForwardX11
/etc/ssh/sshd_config: terminating, 2 bad configuration options
SourcePackage: openssh
That has to be resolved for the install/upgrade of the ass
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
BTW - maybe the target is incomplete - how did you create your target FS
/home/sniper/virtuals/lxc/cont13 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742457
Title:
libvirt cannot run lxc domain
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
** Package changed: firefox (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499924
Title:
ubuntu restart every time when I shutdown it.
To manage notifications about this bug go t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1742488
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Software Updater - How It Should Look
** Attachment added: "Software Updater How It Should Look"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1778726/+attachment/5156786/+files/Software%20Updater%20How%20It%20Should%20Look.png
--
You received this bug notification because yo
Public bug reported:
SUMMARY
There are two expandable sections of the Software Updater window:
1. 'Details of updates'
2. 'Technical description'
When the Software Updater window first opens, the 'Details of updates'
section is not expand vertically, and an empty 'Technical description'
take
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
This still affects Bionic, but it also still is of super low importance.
As even if we would change the default path it would look for, by default slow
queries are not enabled.
They have to be enabled in /etc/mysql/mysql.conf.d/mysqld.cnf first, otherwise
we will just get the same error, but with
Perl file with .sh ending - /me shivers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819535
Title:
mysqldumpslow looking for slow.log file on an incorrect directory
To manage notifications about t
Actually it is easy:
- my $slowlog = ($defaults =~ m/--slow-query-log-file=(.*)/)[0];
+ my $slowlog = ($defaults =~ m/--slow_query_log_file=(.*)/)[0];
That is it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
With the above and slow log enabled in the config it will automatically
work like this:
root@b:/etc/mysql# mysqldumpslow
Reading mysql slow query log from /var/log/mysql/mysql-slow.log
Count: 1 Time=0.00s (0s) Lock=0.00s (0s) Rows=0.0 (0), 0users@0hosts
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Public bug reported:
Description:Ubuntu 18.04 LTS
Release:18.04
clevis-systemd:
Installed: 8-1
Candidate: 8-1
Version table:
*** 8-1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
What I expected to happen: ena
** Changed in: nautilus (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: nautilus (Ubuntu Bionic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Daniel, Thanks for the response. I'm struggling to track down this
issue since it locks up my machine and no logs or errors appear to be
created.
I'll see about posting on systemd github. Thanks for the link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: gnome-software (Ubuntu Bionic)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756379
Title:
Delay start of gnome-software
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Caught a regression error and filed an upstream bug:
https://bugzilla.samba.org/show_bug.cgi?id=13486
** Bug watch added: Samba Bugzilla #13486
https://bugzilla.samba.org/show_bug.cgi?id=13486
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I was having this same bug and I managed to "fix" it by deleting
everything under /var/lib/apt
i.e. sudo apt rm -rf /var/lib/apt/
Then run "sudo apt update" and reboot the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764723
Title:
gnome-initial-setup says that Livepatch is "all set" even if enabling
is still in progress.
To manage n
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Daniel, also please once you've get the working version, propose it to
salsa [1], as for mutter we're in sync with debian
[1] https://salsa.debian.org/gnome-team/mutter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/578112
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751396
Title:
DVR: Inter Tenant Traffic between two networks and conne
Note: This needs more time or more corosync experience for a RCA.
@Erik - if in the meantime you found more on this let us know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733889
Title:
wrong d
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
FYI - submitted upstream via https://github.com/mysql/mysql-server/pull/213
We will pick it up once merged and released in a new version - prio is too low
to consider any SRU IMHO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
101 - 200 of 543 matches
Mail list logo
