[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So in that case the only possible culprits are the charon config file
and the System76 stuff (since presumably it won't actually affect a non-
System76 machine). I can poke around with System76 and see if they know
anything, and we should be able to try a run with the charon config put
back to
@dhookersl I believe that if he ran apt-clone on your file that it would
have installed our custom packages for him, so his environment should be
perfectly identical to yours except for the charon config file (that is
the only config file we don't package).
--
You received this bug notification
** Tags added: id-5b91488653e37e4a1e6b8095
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789977
Title:
Upgrade from 16.04 to 18.04 crashed, required dpkg --configure -a to
recover (multiple
I am almost certain that the lvm2 messages happen in the couple of
minutes before the box crashes/reboots itself. The fact that they
happen over several minutes is part of what makes me think that it's
coincidental and just something that's unhappy because we're in the
middle of installing stuff
I found a couple of crash reports (bug 1767747) in Launchpad regarding
lvm2 and the crash happening on reboot after upgrading to 18.04,
although its possible they only received the notification after
rebooting. Do you happen to know whether the lvm2 crash occurred after
reboot or during the
Neither system had LVM configured at all, which is why I thought it
might be coincidental, but I wanted to include it anyway.
I did have to manually deal with our custom edits to /etc/ssh/ssh_config
and /etc/strongswan.d/charon.conf and System76's custom edits to
/etc/default/grub in order to
How are your LVM2 volumes configured? Based on that segfault, I would
guess that it has something to do with that (and would not necessarily
be reproducible if the volume configuration is not similar).
I would have a hard time believing that it has anything to do with our
custom Debian packages.
Honestly, if this were one system I'd be of the opinion that I recovered
it and it's fine. What's concerning me is that we've seen it on three
systems now and we have a bunch more that need to be upgraded.
The only thing I can think of if it's not reproducible outside our
office is that it's
I haven't found any crash files in /var/crash on either system that I
looked at in detail. It actually sort of acts like a normal 'install
for a while, then reboot', it just comes back up in a half-installed
state after that first reboot, which is why I think it crashed rather
than normally
Are there any crash files in /var/crash/ which are related to the
upgrade process?
I tried recreating the failure by using the apt-clone file attached to
this bug report and then upgrading but I did not receive a crash.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New =>
** Tags added: xenial2bionic
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789977
Title:
Upgrade from 16.04 to 18.04 crashed, required dpkg --configure -a to
12 matches
Mail list logo
