Opened 15 years ago
Closed 15 years ago
#3594 closed defect (fixed)
Virtual Box doesn't start up on Fedora 10
Reported by: | gboethius | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description (last modified by )
Virtual Box encounters an error when starting and shuts down. Reinstalling didn't help. Below is the automatic bug report.
Change History (8)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Description: | modified (diff) |
---|
I have removed the whole crap from the description. gboethius, what exactly does not work for you? Does the VirtualBox GUI failed to start or are you unable to start a VM? andrewz, Please retest this with VirtualBox 2.1.4 because version 2.1.0 is quite old and there are many bugs fixed since this version.
comment:4 by , 15 years ago
andrewz, see that ticket, it's a dkms issue. You might even try VirtualBox 2.2.2.
comment:6 by , 15 years ago
Does that mean that I can close this bug? Why do you need to kill X? Because of that dkms issue?
comment:7 by , 15 years ago
frank: Yes, I have to kill X for the DKMS issue. I found a way to workaround this bug back in VBOX 2.1.0. IIRC, I fixed it with this tip:
sudo yum remove imsettings im-chooser 'scim*
http://forums.virtualbox.org/viewtopic.php?p=65149&sid=1c81bd27fd9132d77220f0ab1133965d#p65149
This may be related https://bugzilla.redhat.com/show_bug.cgi?id=491838
comment:8 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
A few days ago my VirtualBox 2.1.0 manager console no longer started on Fedora 10: it would just hang. I could start individual VM's from the command line using -startvm. Then, I did 'killall imsettings; VirtualBox' and it worked again. I saw a similar report on the VBox forum.
Whoever filed this bug: please post logs as attachments. This page is hard to read.