Custom Query (16363 matches)
Results (1855 - 1857 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9009 | obsolete | gnome Bug 651656 - Complete Loss of access to desktop - gnome 3.0 and Virtual Box 4.0.8 - Fedora 15 | ||
| Description |
I don't know if this is a gnome bug a Virtual Box bug, or both. It is, however, very serious as it causes me to completely lose control of my disktop. I have entered this bug also in the gnome bugzilla under the subject bug number. I am running the latest Fedora 15 with gnome 3.0. This problem did not occur with the previous version; Fedora 14. It apparently was created with the new gnome 3.0 version. Run an operating system in virtualbox in the full screen mode (I am running Windows/XP). In this mode there are no visible controls for gnome. My complete screen is taken up by my windows/xp desktop. I then minimize the virtual box screen using the control that pops up at the bottom of the screen when you mouse over it, and I am now back onto the gnome desktop with no action bar and no way to recover. I can't get back into my virtual box window, and I can't leave the blank background image in gnome. I did finally find a way to recover: I must go to a non-X window (control-alt-f2 etc.) log in there and kill the virtual box process in order to get control back to gnome. Jim Shipman |
|||
| #19546 | invalid | Does not locate installed kernel-header/kernel-devel on Centos81. | ||
| Description |
Fresh build of Centos8, immediately updated (to 8.1 it seems), then installed VB. Started the app, created a VM but it won't load the VM giving the not setup to build kernel module error. I ran /sbin/vboxconfig but the error persistd. As I do not operate with secure boot and DO have the latest version of kernel-headers and kernel-devel not sure what the error can be. I did notice from the script output that VB has a different package name for kernel-devel it recommends: kernel-devel kernel-devel-4.18.0-147.el8.x86_64 installed: kernel-devel-4.18.0-147.8.1.el8_1.x86_64 |
|||
| #17486 | duplicate | Guest Additions break Ubuntu 17.10.1 | ||
| Description |
Installing GA in Ubuntu 17.10.1 reports no build errors, but says "modprobe vboxsf failed" and the system can not be rebooted (hangs). After the GA install, dmesg shows vboxsf: loading out-of-tree module taints kernel. vboxsf: module verification failed: signature and/or required key missing - tainting kernel vboxsf: Unknown symbol VBoxGuestIDC (err 0) VGDrvCommonIoCtl: Unknown request iFunction=.... (and many similar) I will attach a screen-shot with details After reboot, OS hangs with "A start job is running for Hold until boot". This does not occur when rebooting before trying to install GA. It also did not happen with the original Ubuntu 17.10 release. Maybe it has something to do with the work-arounds for Meltdown & Spectre? STEPS TO REPRODUCE: 1. wget http://releases.ubuntu.com/17.10.1/ubuntu-17.10.1-desktop-amd64.iso
(sha1sum: 002d059716f0d0ef33fedd1711f6c86671427747)
2. Create new VM (I took all defaults, except 4GB memory)
Mount ubuntu-17.10.1-desktop-amd64.iso to Optical Drive and start the VM
3. (boots from iso) Click "Install Ubuntu"
Do not check any extra download options. Click Continue
Check "Erase disk and install Ubuntu", "Install Now"
Create test user, check "Log in automatically"
When prompted, click "Restart Now", then press ENTER when prompted.
(Hangs as it always does, due to some unrelated issue)
Machine->Reset
4. (OS boots from virtual disk)
Click dot-grid-icon, type "updater", click the "A" icon, install updates
(Note: It will appear to hang with "Waiting for packagekitd to exit" but
continues by itself after several minutes)
Click "Restart Now"
5. dot-grid-icon->"terminal"
sudo apt-get update
sudo apt-get install build-essential
PowerIcon(upper right)->PowerIcon->Power Off
6. Take a snapshot so you can get back to this state.
Restart the VM
7. Devices->Insert Guest Additions CD image...
Click "Run" and enter pw when prompted
RESULTS:
VirtualBox Guest Additions: modprobe vboxsf failed
dmesg shows many errors, e.g. "Unknown symbol VBoxGuestIDC"
(see screenshot)
System hangs during subsequent reboot
|
|||

