I know I don’t need Windows to compile for Windows, but I’m writing /
updating those instructions for Windows users. Currently the Ubuntu 16
instructions tell the user to add sources from a newer release, which
could cause problems.
--
You received this bug notification because you are a member
Current instructions for reference:
https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md
Maybe a Virtual Box on Windows would be an alternative.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Ubuntu 18 in a Virtual Box directly on my Mac works fine.
However, I'm trying to make it easier for Windows 10 users to compile
the Bitcoin Core application from source. This is currently problematic
with Ubuntu 16, so I'm trying to see if it can be made to work with
Ubuntu 18 (at least once
> Do you mean you used Ubuntu app from the Windows store
Correct.
So my setup is:
iMac running MacOS 10.13.3
Virtual Box 5.2.6
VM running Windows 10 Home Edition
Then on Windows 10 I install Ubuntu from the Windows store and then ran:
do-release-upgrade -d
I tried the latter command
Public bug reported:
This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting
to upgrade to 18.04.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 235-3ubuntu3
ProcVersionSignature: Microsoft
ack to Event.
This is not the case. Even today, one of the machines is showing the
message from the wrapper that indicates the DHCP lease was not correctly
applied according to the journal:
➜ sjors@cuba ~ cat /tmp/nm-helper-retries.log
Tue Nov 14 07:23:07 CET 2017: needed 5 attempts to update NetworkManager
(REN
Hi Sebastien, thanks for your comment!
I've reported the bug upstream as GNOME #784636, see
https://bugzilla.gnome.org/show_bug.cgi?id=784636. I already added a
bugwatch.
** Bug watch added: GNOME Bug Tracker #784636
https://bugzilla.gnome.org/show_bug.cgi?id=784636
** Also affects:
I've closed down on the root cause being the /usr/lib/NetworkManager/nm-
dhcp-helper tool. Occasionally, this binary runs, but fails to correctly
send the update to NetworkManager. No errors occur when this happens;
NetworkManager in debug mode just says "accepted connection on private
socket"
** Summary changed:
- NetworkManager seems to drop IPv4 DHCP lease even though it was successfully
renewed
+ NetworkManager does not update IPv4 address lifetime even though DHCP lease
was successfully renewed
--
You received this bug notification because you are a member of Ubuntu
Touch
By setting log_level to DEBUG, I could confirm from the logs that there
is a miscommunication between dhclient and NetworkManager causing this
issue.
It looks like it is not NetworkManager that removes the IPv4 address
from the interface; the address is removed from the interface
automatically by
Public bug reported:
I've found an issue on some of our Xenial office machines, causing
NetworkManager to drop its IP address lease in some cases when it
shouldn't. I'm not sure if the actual bug is in NetworkManager or
perhaps dbus or dhclient, but I'll do my best to help to figure out
where it
Can confirm this with DHCP instead of BOOTP as well:
Apr 19 17:51:48 curacao dhcpd[18031]: reuse_lease: lease age 671 (secs) under
25% threshold, reply with unaltered, existing lease
Apr 19 17:51:48 curacao dhcpd[18031]: DHCPDISCOVER from 08:00:27:44:28:00 via
eth0
Apr 19 17:51:49 curacao
12 matches
Mail list logo
