> Reg output logs, do you mean from the current running system?
Generally one wants logs from after reproducing the error condition
since that has a high chance of showing an error or warning indicating
what the problem might be. Logs from a normal operational situation can
sometimes be of
Hi and sorry being slow, been away a few days.
ssh can be a little tricky, I have 2 firewalls,
one from ISP and my own and then running a VM.
Reg output logs, do you mean from the current running system?
I have turned off updates now since it will kill the system for now.
If it do the update the
I filed an internal bug to track this. As recommended by Christian, we
need logs from /var/log/vmware-*.log and and the output of 'sudo
journalctl' to see what's going on here. It looks like it's reproducible
from the backup, so if ssh login is not enabled yet, try to repro with
that enabled and
Hi Lars,
the latest would be [1] 10.3.10 as verified to be ok by VMWare.
It was published in mid June, if you didn't do updates before it is possible
that this might be the first time you use the new version.
Upgrading the tools in a guest of my own works fine, so we need to find
what exactly is
Quote:
"4) When starting the VM it comes as far as starting the graphical interface
just befor showing the login. It just hangs from there, can only be turned off."
So how could we get some state info from there.
I assume you have no means whatsoever to e.g. get to the main console via
** Package changed: ubuntu-release-upgrader (Ubuntu) => open-vm-tools
(Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836500
Title:
open-vm-tools
To manage
