This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.15.3
---
ubuntu-release-upgrader (1:19.10.15.3) eoan; urgency=medium
* do-release-upgrade: add linux-base to the check for required reboot after
a kernel upgrade (LP: #1844805).
-- Łukasz 'sil2100' Zemczak
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.36
---
ubuntu-release-upgrader (1:18.04.36) bionic; urgency=medium
* do-release-upgrade: add linux-base to the check for required reboot after
a kernel upgrade (LP: #1844805).
ubuntu-release-upgrader
This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.9
---
ubuntu-release-upgrader (1:19.04.16.9) disco; urgency=medium
* do-release-upgrade: add linux-base to the check for required reboot after
a kernel upgrade (LP: #1844805).
ubuntu-release-upgrader
This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.29
---
ubuntu-release-upgrader (1:16.04.29) xenial; urgency=medium
* do-release-upgrade: add linux-base to the check for required reboot after
a kernel upgrade (LP: #1844805).
ubuntu-release-upgrader
I have performed the same verification of ubuntu-release-upgrader
1:16.04.29 on xenial. I have enabled xenial-proposed, upgraded (pulling
a new kernel), ran `do-release-upgrade` and got the message that a
reboot is required first. Situation similar to bionic. Good to go.
** Tags removed:
I have verified ubuntu-release-upgrader 1:18.04.36 on bionic. I have
enabled bionic-proposed, upgraded (pulling a new kernel), ran `do-
release-upgrade` and got the message that a reboot is required first. I
then double-checked the /var/run/reboot-required.pkgs contents - it only
had 'linux-base'
I have verified ubuntu-release-upgrader 1:19.04.16.9 on disco. I have
enabled disco-proposed, upgraded (pulling a new kernel), ran `do-
release-upgrade` and got the message that a reboot is required first.
All good.
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
I have verified ubuntu-release-upgrader 1:19.10.15.3 on eoan. As
previously, I have enabled eoan-proposed, upgraded (pulling a new
kernel), ran `do-release-upgrade` and got the message that a reboot is
required first.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
The bug mentioned in comment #42 is unrelated, the failure is caused by
the usual "ERROR No 'ubuntu-minimal' available/downloadable after
sources.list rewrite+update", most probably meaning a modified/corrupted
sources.list file.
** Tags removed: verification-failed-xenial
--
You received this
Hello Jonathan, or anyone else affected,
Accepted ubuntu-release-upgrader into eoan-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:19.10.15.3 in a few hours, and then in the
-proposed repository.
Please help us by testing
Uploaded a modified version of the update, hopefully supporting all the
cases of kernel upgrades.
** Changed in: ubuntu-release-upgrader (Ubuntu Disco)
Status: Fix Committed => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Eoan)
Status: Fix Released => In Progress
**
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.15.2
---
ubuntu-release-upgrader (1:19.10.15.2) eoan; urgency=medium
* Fix binary and binary-indep targets to work as intended (LP:
#1850851)
ubuntu-release-upgrader (1:19.10.15.1) eoan; urgency=medium
*
I tried verifying this on bionic, but actually I need to look into it a
bit more closely - since after upgrading the system (with a new kernel
from -proposed as well), I noticed that /var/run/reboot-required.pkgs
does not actually list linux-image-* in it, but instead only has a
'linux-base' entry
I have successfully verified ubuntu-release-upgrader 1:19.04.16.8 on a
disco multipass instance. Enabled disco-proposed, upgraded all the
packages (the upgrade also pulled in a new kernel from -proposed), ran
do-release-upgrade and confirmed that a reboot is required. And after
rebooting the
Hello Jonathan, or anyone else affected,
Accepted ubuntu-release-upgrader into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.04.28 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from
19.04 to 19.10
To manage
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail during
I tested te new package on a clean Eoan Install:
1. Install Ubuntu 19.10 Eoan
2. Install the virtualbox package
3. Enable eoan-proposed
4. Install updates
5. do-release-upgrade -d
6. "refusing upgrading before a reboot is performed" worked fine
** Tags removed: verification-needed-eoan
** Tags
** Tags removed: regression-release
** Tags added: dist-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from
** No longer affects: virtualbox (Ubuntu)
** No longer affects: virtualbox (Ubuntu Disco)
** No longer affects: virtualbox (Ubuntu Eoan)
** No longer affects: virtualbox (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Jonathan, or anyone else affected,
Accepted ubuntu-release-upgrader into eoan-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:19.10.15.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Jonathan, or anyone else affected,
Accepted ubuntu-release-upgrader into disco-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:19.04.16.8 in a few hours, and then in the
-proposed repository.
Please help us by testing
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.1
---
ubuntu-release-upgrader (1:20.04.1) focal; urgency=medium
[ Brian Murray ]
* DistUpgrade/{EOL,Devel}ReleaseAnnouncement,
DistUpgrade/window_main.ui,
data/gtkbuilder/DistUpgrade.ui,
** Also affects: virtualbox (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu Disco)
Status: New => Triaged
** Changed in:
** Description changed:
+ [Impact]
+
+ Currently some users can encounter an error while upgrading from disco
+ to eoan whenever the kernel has been upgraded before starting the
+ upgrade without a reboot first. This can cause certain dkms packages
+ (like virtualbox-dkms) in certain
** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
** Changed in: ubuntu-release-upgrader (Ubuntu Eoan)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
@kneutron were you in the state described above, i.e., had you updated
your 19.04 kernel but not rebooted after doing so before doing the 19.10
upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update: I did *not* run into this bug again while doing do-release-
upgrade from 19.04 to 19.10 today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms,
** Tags added: id-5db1d1e0a5035a6075816b57
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from
19.04 to 19.10
To
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Triaged
** Tags removed: rls-ff-incoming
** Also affects: virtualbox (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects: ubuntu-release-upgrader (Ubuntu Focal)
Importance: Medium
On Wed, Oct 23, 2019 at 07:13:27PM -, Brian Murray wrote:
> It sounds like we should be for checking something else in the reboot-
> required.pkgs file. What would that be?
It looks like linux-image-* shows up in there, seems like a reasonable
thing to check for in this case.
--
You
do-release-upgrade contains the following code:
190 if os.path.exists('/var/run/reboot-required.pkgs'):
191 reboot = False
192 with open('/var/run/reboot-required.pkgs', 'rb') as f:
193 for line in f:
194 if line == b'libc6\n':
195 reboot = True
196
So the failure mode I ran into was running the upgrade to 19.10 after
upgrading all disco packages but before rebooting.
In that case it seems like the upgrader needs to refuse to run if the
system needs to be restarted?
--
You received this bug notification because you are a member of Ubuntu
I see there's one caveat, the autoinstall_all_kernels variable in
/etc/dkms/framework.conf can be set to build for all installed kernels,
not just the current and newest. But the default is to build only for
current and newest.
--
You received this bug notification because you are a member of
Modules should only be built at install time for the current and newest
kernels. So as long as you are up to date _and_ booted into a kernel
with the fix you should be able to upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was fully updated in disco before I upgraded to 19.10.
I think the problem is that it's not good enough for the tip disco
kernel to be updated. One old kernel version is saved even after
autoremove, and if the user doesn't run autoremove then I think any
number of old kernels could be saved,
The disco kernel was updated for this, but it looks like you were
running an older kernel which did not receive the update. If you reboot
into the newest kernel for disco you should not encounter this issue
when upgrading.
--
You received this bug notification because you are a member of Ubuntu
If the system was updated to the tip of disco before being upgraded as
above this should not occur as the kernel in disco was fixed to avoid
this issue. I was under the impression you had to be updated to the
latest -updates packages to do an upgrade, so I am supprised it let you
do this.
--
Wow, Gianfranco.
As someone who works on Debian / Ubuntu would it not be preferable for
you to make at least a modicum of effort to route an issue like this to
the appropriate people rather than merely repeatedly trying to close the
bug report?
In the short time since 19.10 was officially
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
*sigh*
The bug is not that the version of virtualbox in 19.10 only works with
the 19.10 kernel.
The bug is that if someone with virtualbox tries to upgrade to 19.10,
THE UPGRADE WILL FAIL BECAUSE OF THIS.
The upgrade needs to handle this problem, not just fail with no useful
explanation to the
You have to move to kernel 5.3, the kernel 5.0.0-23 didn't have the
fstack protector fixes
** Changed in: virtualbox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is similar to
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1844805
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail
Gianfranco, FYI, I missed the notification about your comment above
because of https://bugs.launchpad.net/launchpad/+bug/1589693. You might
want to weigh in there and/or vote on that bug if you haven't already.
Launchpad has been generating emails that violate email security
standards for over
Here's what I get trying to build the eoan virtualbox dkms module
against an installed disco kernel.
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1844805/+attachment/5290832/+files/make.log
** Changed in: virtualbox (Ubuntu)
Status:
Hello, do you think you can attach also the referenced file?
/var/lib/dkms/virtualbox/6.0.12/build/make.log
thanks
** Changed in: virtualbox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844805
Title:
virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from
19.04 to 19.10
To manage
48 matches
Mail list logo
