Custom Query (16363 matches)
Results (2398 - 2400 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4409 | fixed | Segmentation Fault VB 3.0.0 on Fedora Core 11 | ||
| Description |
Recently I have upgrades to VirtualBox 3.0.0 (build 49315) on my Fedora Core 11 Linux server and cannot start VirtualBox anymore. Symptoms are that starting from GNome system menu, won't show any window. Starting VirtualBox from a terminal window will very quickly show a big window, which disappears again showing "Segmentation fault" in the terminal window. I have removed VirtualBox from the system using "rpm -e", rebooting and reinstalling it. Same problem. The system in question is an Intel N330 dual-core with 2 GB Ram. I do have a VBox.log on the system, but that relates to a VM startup prior to the 3.0.0 upgrading. I will attach a coredump file that I found as a result of a start action. Kind regards, Rende |
|||
| #4412 | fixed | freezing of ubuntu 8.04, 8.10 and 9.04 | ||
| Description |
when installing updates from the package management the sysem is crashing if some packages are downloaded. |
|||
| #4413 | fixed | VirtualBox 3.0 reboots system with RHEL 5.3 x64 host OS | ||
| Description |
I just upgraded to VirtualBox 3.0 on a RHEL 5.3 machine 64-bit, and when I try to start it up, it brings the whole machine down (hard re-boot). I'm going to revert to 2.2.4 for now... the only thing I can find are a few lines in /var/log/messages:
Jul 6 12:19:20 lx57 kernel: VBoxDrv: dbg - g_abExecMemory=ffffffff88e6db00 I can't get a core dump because it crashes hard, I don't even get a VBox.log file. This is kernel 2.6.18-128.1.16.el5 |
|||

