| 1 |
On Saturday, 27 November 2021 12:59:49 GMT Wols Lists wrote: |
| 2 |
> On 27/11/2021 12:41, Peter Humphrey wrote: |
| 3 |
> > On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote: |
| 4 |
> >> Simple problem, after a kernel upgrade, virtualbox no longer works. This |
| 5 |
> >> is to be expected, of course, BUT ... |
| 6 |
> >> |
| 7 |
> >> How do I fix it !!! |
| 8 |
> >> |
| 9 |
> >> What I always did on my old system was to re-emerge the modules. |
| 10 |
> >> |
| 11 |
> >> The docu says "emerge @module-rebuild". |
| 12 |
> >> |
| 13 |
> >> Both of these terminate with "nothing to rebuild". |
| 14 |
> >> |
| 15 |
> >> What else can I do? |
| 16 |
> > |
| 17 |
> > You could try 'emerge @x11-module-rebuild'. |
| 18 |
> |
| 19 |
> Same result - nothing to rebuild :-( |
| 20 |
> |
| 21 |
> Cheers, |
| 22 |
> Wol |
| 23 |
|
| 24 |
It may be worth mentioning ... I've noticed my MSWindows VirtualBox VMs are |
| 25 |
malfunctioning when I launch them from within Plasma Wayland. I can login, |
| 26 |
but then lose the ability to click on anything or interact with the Windows |
| 27 |
desktop. Things work fine when I run them within Plasma in Xorg instead of |
| 28 |
Wayland. |
Archives