I am affected by the same bug. Some extra information:
- tapping definitely does something, as brief animation can be seen (icons
flying away and back from button)
- Sometimes tapping on icons switches on drag and drop mode (and stays like
that), even though tap itself was short
- I have
Public bug reported:
I want upgrade from 16.04.5 lst to 18.04.1 lst
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: zfs
This bug is affecting my job. I am not able to encrypt or sign my
e-mails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771880
Title:
Seahorse unable to import certificates in Ubuntu 18.04
To
Hello,
unfortunately this problem still exists.
ubuntu 16.04 & Thunderbird 52.8.0 (64bit).
I can not run apport-collect temporarily.
Regards
Am 03.07.2018 um 00:30 schrieb gf:
> Hello Mac-e-mac,
> Thank you for submitting this bug and reporting a problem with Thunderbird
> and lightning.
>
>
@Kovács Viktor, this report is not only about "original" problem, but
all the problems affected by current implementation. I described other
one with modifier for national characters, once you define such key you
cannot use it as shortcut modifier.
--
You received this bug notification because
Public bug reported:
Not sure if this is intended, but it's not possible to install two
architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04
and 18.04 apt-get says that they are in conflict.
The package is a dependency for libegl1-mesa-dev, which I need to have
installed in 64
This is a known problem with the official Ubuntu package. We can only
recommend switching to our PPA: http://kicad-pcb.org/download/ubuntu/
You can find more details here:
https://bugs.launchpad.net/ubuntu/+source/kicad/+bug/1767652
Please complain in the Ubuntu report, hopefully it can help fix
Fedora policy disallows us from adding /snap automatically. Please
create the symlink manually.
OTOH we might consider making the error message more intuitive and
suggest that the user take action if so desired.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
You need to do `snap refresh --beta core` for now. Hopefully it's not
long before it's in the stable channel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175
Title:
some snaps fail on
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175
Title:
some snaps fail on vulkan/icd.d permission error
To manage
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
*** This bug is a duplicate of bug 1700560 ***
https://bugs.launchpad.net/bugs/1700560
** This bug has been marked a duplicate of bug 1700560
“snap find” returns confusing results
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Neal has pushed an update to 2.30. From what Zyga reported, things
looked very good.
Can fetch the packages from here and verify on your machine?
https://bodhi.fedoraproject.org/updates/?packages=snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: snappy
Status: New => Invalid
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666873
Title:
Snap icon is not
** Changed in: snappy
Importance: Undecided => Wishlist
** Changed in: snappy
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669012
Title:
Can't reinstall a snap
** Changed in: snappy
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/1667829
Title:
console-conf v0.0.5 crashes if no config needed
To manage notifications about
** Changed in: snappy
Importance: Undecided => Wishlist
** Changed in: snappy
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682446
Title:
lvm is not available on
Public bug reported:
In the old /etc/network/interfaces I could define a virtual interface:
auto eth0
iface eth0 inet static
address aaa.aaa.aaa.aaa
netmask 255.255.255.0
gateway aaa.aaa.aaa.1
auto eth0:0
iface enp7s0f0:0 inet static
address
Opened a PR https://github.com/snapcore/snapd/pull/4432 that should
address the problem on Fedora and other distributions where snapd
libexedir is different from /usr/lib/snapd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem on Fedora needs further investigation. Given how classic
snaps are packages, this may easily be a problem with the snap itself.
FWIW. teleconsole 0.3.1 (3) seems to work just fine on Arch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1713717 ***
https://bugs.launchpad.net/bugs/1713717
I get the same crash as mentioned here. I would like to follow the original bug
(as this is marked as a duplicate).
Could someone provide upstream/bugs.kde.org number?
--
You received this bug
Adding my experience in case someone has the same issue.
Installed a fresh Ubuntu 16.04.3 with the clear entire drive and set up
LUKS+LVM option. After the first reboot I got the graphical password
prompt but couldn't type anything. After the next reboot, after passing
GRUB, the screen just
Public bug reported:
please help me, i can't update my ubuntu
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libmagickcore-6.q16-2:amd64 8:6.8.9.9-7ubuntu5.7
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
I tested sssd-1.13.4-1ubuntu1.4 on xenial on a bare metal machine
equipped with Intel X550T, a network controller notorious for long and
somewhat random startup initialization time. I am happy to report that
autofs boot problems still occur, but at a much diminished rate. While
previously autofs
Here are the results on my tests of package sssd-1.13.4-1ubuntu1.3 on
Xenial.
As I noted in comment #20, this bug report involves two separate issues, both
contributing to failure of autofs to properly start on boot:
1. autofs starts before sssd.
2. autofs starts after sssd, but before sssd
Huang YangWen: can you attach result of those command:
ls -l /sys/bus/acpi/devices/
sudo lspci -vvnn
I wonder what the differences between motherboards are. I suspect Gigabyte has
something other boards don't have.
--
You received this bug notification because you are a member of Ubuntu
> Maciej, do you have any suggestions if there is no previous OS
installed?
You may try to boot with those options:
acpi=off quiet loglevel=3
(just acpi=off might be enough). That should get you through
installation.
--
You received this bug notification because you are a member of Ubu
I did brief testing of sssd-1.13.4-1ubuntu1.3 on Xenial. Autofs still
fails to properly start on boot, but I am not sure which of the numerous
issues described in this bug report contributes to the failure now. I
will do more testing after the weekend.
--
You received this bug notification
I've found a workaround (requires compiling own kernel, tested on 4.11
and r4.11rc1):
When configuring kernel (I used make menuconfig) disable following
things:
Everything under device drivers/gpio support, especially:
memory mapped files/amd promontory support (GPIO_AMDPT)
and pci gpio
The issue had nothing to do with upgrades, its the same problem on 16.10 as
well as on 17.04.
I've tested it on my system and on live ubuntu on usb.
I've tried to use mainline kernel and the problem is still there.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
apport information
** Tags added: apport-collected zesty
** Description changed:
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3
motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as
I've added appport info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360
Title:
System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
To manage notifications about this bug
Public bug reported:
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3
motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of
Robie, thank you for your comment.
There is a number of bugs related to autofs and sssd present in Xenial. A
partial attempt to sort out this situation can be found in bug 1566508, comment
#20 (https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/comments/20 ).
However, this is
I do not use Debian, but please feel free to file a bug report with
them. Regarding the autofs.service file attached above, please note that
it would benefit from inclusion of additional services in the After=
line (such as nslcd, slapd and NIS). The reason that I did not include
them is that
Andrei, I'm glad that you found my workaround useful. I did not
experience problems that you describe (I did not test these issues on a
laptop), but I agree that they are relevant to this bug. If you could
subscribe to notifications about this bug, we would get more bug heat
points, and hopefully
Victor, thanks a lot for the explanation. I apologize for not
volunteering to test your patch, but it fixes an issue (#2) that I am
unable to reproduce in Xenial. But I really appreciate your efforts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Victor, would you be so kind to post a link to your patch, and also tell
us which of the numerous issues discussed in this bug report (comment
#20) are solved by the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Is it a daft question to ask why it works for them and not you ?
This is a very good question. My take on it is as follows.
There are several issues here, and the majority are related to startup
configuration. Speaking of Ubuntu 16.04, the problem is that Ubuntu
first switched from SysV
Public bug reported:
Currently package zfsutils-linux contains systemd target file
/lib/systemd/system/zfs.target that specifies following dependencies:
Requires=zfs-mount.service
Requires=zfs-share.service
Wants=zed.service
zfs-share.service is not essential in setups where file sharing is not
Here is my attempt to sort out how many bugs are related to autofs
failing on boot.
This bug (1566508)
As noted earlier, these are actually two issues:
1. autofs starts before sssd.
2. autofs starts after sssd, but before sssd responders are up.
On Trusty, I observed #1 and #2, and on Xenial I
Public bug reported:
This problem is occurring on Ubuntu 16.04 system where autofs and sssd
are both installed, sssd is configured to provide automount maps, and
nsswitch.conf directs autofs to use sssd. In a situation when both sssd
and autofs start before network is up (which happens
Public bug reported:
Package autofs in Ubuntu 16.04 includes SysV startup script
(/etc/init.d/autofs) and Upstart unit (/etc/init/autofs.conf), but does
not include systemd service file. As a result, systemd starts autofs as
part of its LSB (sysv) processing, which makes it difficult to ensure
This problem occurs because on Ubuntu 16.06 both sssd and autofs are started
too early, before network is up. This has been observed in setups with network
interfaces configured statically in /etc/network/interfaces (is that your setup
as well?) Sssd itself recovers from this condition
Issues related to ifup and service files included in ifupdown package
are reported as bug 1588915.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Title:
autofs races with sssd on startup
To
I am also affected by this issue. In my case both network.target and
network-online.target are reached too early, which results in sssd and
autofs to start before network interfaces are up; autofs then fails to
obtain mount maps and does not attempt to retry; it is necessary to
restart autofs
In order to test whether the bug which is the subject of this bug report
(i.e. "no mounts in table", not "setautomntent") occurs in Xenial with
systemd, I created autofs.service as attached below. This way I could
dispense with /etc/init.d/autofs and directly control when autofs is
started. I can
Here is the autofs.service file mentioned above.
** Attachment added: "autofs.service"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+attachment/4719398/+files/autofs.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Jakub, the "setautomntent" message occurs at the same time when autofs
fails to mount shares on startup. So, while itself it is not a bug and
nobody here suggests that the message should be silenced, it is
nonetheless one of the symptoms of the problem, which is caused most
likely by a number of
Victor, you are right saying that we are dealing with more than one bug
here. It appears to me that we have 3 or 4 separate bugs all conspiring
to prevent autofs from starting in the configuration as described above.
I think that the "setautomntent" error message is a symptom of a
different bug
Jakub, thanks for the information.
Launchpad mangles the URL that you posted in an attempt to hide email addresses
from public view, here it is in an equivalent form that does not include '@':
I finally had a chance to test this issue in Ubuntu 16.04. In a setup
described as in the bug description above, autofs still won't start
correctly, and this is a result of the whole string of problems. Most of
them appear to be separate bugs, but I will list them here for
completeness:
1. ifup
It appears that GnuTLS initialization is failing with an error, perhaps because
there is something in your slapd configuration that newer version of GnuTLS (in
xenial) does not like.
Can you post your slapd config? Please redact it so that it does not contain
any host names, IP addresses, user
I can confirm that the following packages from xenial-proposed fix the bug:
slapd 2.4.42+dfsg-2ubuntu3.1
libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1
ldap-utils 2.4.42+dfsg-2ubuntu3.1
I did not test the packages in wily-proposed. Setting the test
environment is not trivial, and I don't think it is
Chris, thank you very much for preparing the packages for -proposed
repos. I started testing of xenial-proposed version, but tests are not
progressing quickly, due to issues that I described above. In addition I
have run into another problem, likely unrelated to this bug, which is
further
Due to the nature of this bug (referencing previously freed memory
leading to an undefined behavior), a reliable testing procedure is
difficult to create. This bug was originally found by looking for a
cause of syncrepl failures. The reproducibility of these failures was
about 50%, enough to make
Public bug reported:
When i try to update system from 15.10 to 16.04 it shows me:
" An unresolvable problem occurred while calculating the upgrade. This
can be caused by: * Upgrading to a pre-release version of Ubuntu *
Running the current pre-release version of Ubuntu * Unofficial software
Same problem with plain ext4 root partition. I have two systems
configured very similarly with 16.04, one has this problem and another
has not. But their hardware is different, so I'd make an educated guess
that this is a timing issue. Good thing is that it appears benign.
BTW, I get three
** Changed in: nova
Assignee: Maciej Szankin (mszankin) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a n
I reported the bug to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820244
** Bug watch added: Debian Bug tracker #820244
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820244
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> I believe that is all tied together. php7.0 and php5 conflict with one
another in apache's configuration.
I see that the root of the problem was that apt did not remove php5
while installing php7.0.
> Right, but you're running a not-yet-released Ubuntu :)
Yes, of course. I've been running it
Thank you for a quick response. Yes, I can find "ERROR: php5 module
already enabled, not enabling PHP 7.0" in /var/log/apt/term.log. Not
sure if this is relevant, but before I ran "a2enmod php7.0", directory
/etc/apache2/mods-enabled contained a link php7.0.load, but did not
contain php7.0.conf.
** Description changed:
After phpldapadmin package dependencies have been switched to php7.0
- (LP: #1564121), a routine package update (apt-get update; apt-get
+ (LP: #1564121), a routine package update (apt-get upgrade; apt-get
autoremove) causes phpldapadmin's web interface to stop working
** Description changed:
After phpldapadmin package dependencies have been switched to php7.0
- (LP: #1564121), a routine package update (apt-get update; apt-get
+ (LP: #1564121), a routine package update (apt-get upgrade; apt-get
autoremove) causes phpldapadmin's web interface to show a
** Patch added: "autofs.conf.diff"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+attachment/4625148/+files/autofs.conf.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566508
Public bug reported:
This report concerns a configuration where autofs and sssd are both
installed, sssd is configured to provide automount maps, and
nsswitch.conf directs autofs to use sssd. In such a configuration autofs
often fails on boot complaining "no mounts in table". This is because
This update to package phpldapadmin causes two problems. As this bug report has
been closed, I reported them as new bugs:
Bug 1566481 phpldapadmin missing dependency php7.0-xml
Bug 1566491 phpldapadmin fails to enable php7.0 module
If you are affected by one or both of these bugs, please post
Public bug reported:
After phpldapadmin package dependencies have been switched to php7.0
(LP: #1564121), a routine package update (apt-get update; apt-get
autoremove) causes phpldapadmin's web interface to stop working and
display a page indicating that php is not enabled.
Workaround: a2enmod
** Description changed:
- After phpldapadmin package dependencies have been switched to php7.0 (LP
- #1564121), a routine package update (apt-get update; apt-get autoremove)
- causes phpldapadmin's web interface to show a warning about missing XML
- support.
+ After phpldapadmin package
Public bug reported:
After phpldapadmin package dependencies have been switched to php7.0
(LP: #1564121), a routine package update (apt-get update; apt-get
autoremove) causes phpldapadmin's web interface to show a warning about
missing XML support.
Workaround: apt-get install php7.0-xml
$
I created patched openldap packages for xenial, available on the same
PPA as above. I tested amd64 packages on xenial beta 2.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557248
I created a PPA with patched openldap packages for wily and xenial. If
you would like to test them, there is more information in bug 1557248.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547927
I created patched openldap packages for xenial, available on the same
PPA as above. I tested amd64 packages on xenial beta 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557248
Title:
OpenLDAP:
I created a PPA with patched openldap packages for wily and xenial. If
you would like to test them, there is more information in bug 1557248.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
I have just found that Howard Chu of OpenLDAP team had already uploaded this
patch to Launchpad VCS:
http://bazaar.launchpad.net/~vcs-imports/openldap/master/revision/20757
Hopefully we will have the package released soon.
--
You received this bug notification because you are a member of Ubuntu
I have just found that Howard Chu of OpenLDAP team had already uploaded this
patch to Launchpad VCS:
http://bazaar.launchpad.net/~vcs-imports/openldap/master/revision/20757
Hopefully we will have the package released soon.
--
You received this bug notification because you are a member of Ubuntu
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557248
Title:
OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code
To manage
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557248
Title:
OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code
To manage notifications about
I created a PPA with patched deb packages, available at:
https://launchpad.net/~maciej-puzio/+archive/ubuntu/openldap
Currently it contains openldap-2.4.41 source package with the above patch
applied, as well as binary debs built from it, for amd64 and i386. These
packages are for Ubuntu 15.10
I created a PPA with patched deb packages, available at:
https://launchpad.net/~maciej-puzio/+archive/ubuntu/openldap
Currently it contains openldap-2.4.41 source package with the above patch
applied, as well as binary debs built from it, for amd64 and i386. These
packages are for Ubuntu 15.10
Patch created by OpenLDAP team applies cleanly to openldap 2.4.41+dfsg-
1ubuntu2 (wily).
** Patch added: "tls_g.patch"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557248/+attachment/4607004/+files/tls_g.patch
--
You received this bug notification because you are a member of
Patch created by OpenLDAP team applies cleanly to openldap 2.4.41+dfsg-
1ubuntu2 (wily).
** Patch added: "tls_g.patch"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557248/+attachment/4607004/+files/tls_g.patch
--
You received this bug notification because you are a member of
Public bug reported:
fresh 64-bit 16.04 Installation on HP Compaq 6720s. The drivers for BCM4311
802.11b/g was working with 14.04 and 15.10 ubuntu version. For 16.04 it is
sometimes working and sometime it doesn't work. Even if it is direct by the
modem it is not connecting to the modem. It is
A bug has been found in libldap code that interferes with the value of
"require cert" option. It affects libldap built with GnuTLS, as is done
in packages supplied by Ubuntu and Debian. The bug causes the value to
be read from previously freed memory, often resulting in incorrect or
random value
A bug has been found in libldap code that interferes with the value of
"require cert" option. It affects libldap built with GnuTLS, as is done
in packages supplied by Ubuntu and Debian. The bug causes the value to
be read from previously freed memory, often resulting in incorrect or
random value
Perhaps the issue is that your certificates have too short RSA keys. In
GnuTLS SECURE256 requires at least 3072-bit public key. Unfortunately,
this is not clearly documented.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Perhaps the issue is that your certificates have too short RSA keys. In
GnuTLS SECURE256 requires at least 3072-bit public key. Unfortunately,
this is not clearly documented.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in
Public bug reported:
May I ask that you backport an upstream patch that resolves the issue of
use-after-free in libldap that interferes with syncrepl, causing
failures and segfaults.
OpenLDAP commit: 283f3ae1713df449cc170965b311b19157f7b7ea
Link:
Public bug reported:
May I ask that you backport an upstream patch that resolves the issue of
use-after-free in libldap that interferes with syncrepl, causing
failures and segfaults.
OpenLDAP commit: 283f3ae1713df449cc170965b311b19157f7b7ea
Link:
#18 worked for me. Thanks Juan!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546176
Title:
Dropbox icon not working on Xubuntu 14.04
To manage notifications about this bug go to:
Linux Mint 17.3 Cinnamon. Indicator works as is, but it's not active,
there is no menu after right/left click.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546176
Title:
Dropbox icon not working
Thunderbird 38.5.1 w/ Linux Mint cinnamon 17.3 no notification, no
audio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491249
Title:
Regression: Visual new email notification no longer working in
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
host
To
First thing - title is confusing. Problem is not in hostname length that
is provided as target in live-migration command. Maximum hostname length
is 64, and verified, it works.
Second thing - providing FQDN (which usually is used for hypervisor
hostname) in live migration does not work by design.
First thing - title is confusing. Problem is not in hostname length that
is provided as target in live-migration command. Maximum hostname length
is 64, and verified, it works.
Second thing - providing FQDN (which usually is used for hypervisor
hostname) in live migration does not work by design.
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a n
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostn
Public bug reported:
I was iinstalling Ubuntu 14.04.3 LYTs and using script sanickkiost
trying to get kiosk on my work. On VM it runs perfectly but on phy
hardware is halted . Asus UN42 computer and Hyundai D32AM display.
Regards,
Maciek
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package:
This indeed is a java version issue. Downgrading to OpenJDK JRE 7u71
solves it. See
https://bugs.launchpad.net/opencontrail/+bug/1481112
http://lists.opencontrail.org/pipermail/dev_lists.opencontrail.org/2015-January/001880.html
Maciej
--
You received this bug notification because you
301 - 400 of 842 matches
Mail list logo
