Custom Query (16363 matches)
Results (793 - 795 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1344 | fixed | Forgiven letters in french translation. | ||
| Description |
On this screenshot I underline in red the errors : http://www.enregistrersous.com/images2/124315659820080317171025.png Indeed the word "prérence" should be like this : "préférence". It was discovered on a Virtualbox 1.5.2, on Ubuntu Gusty Gibbon. PS : You think it as well, I'm french, so I don't speak so english ... Good afternoon. |
|||
| #1348 | fixed | Guest will not start: Assertion Failed | ||
| Description |
I get this error whether starting or clicking on settings. The directory mentioned does not exist. This is version 1.56 on Gentoo x86_64 w/2.6.24 kernel. The vdi image was used in Kubuntu 7.10 32bit, so I tried cloning also but received the same result. Thanks! Assertion failed: [mIPCSem >= 0] at '/home2/vbox/vbox/1.5-lnx64-rel/src/VBox/Main/MachineImpl.cpp' (8058) in nsresult SessionMachine::init(Machine*). Cannot create IPC semaphore, errno=38. Please contact the product vendor!. Result Code: 0x80004005 |
|||
| #1349 | fixed | Using NAT with XP Pro (WinALL?) guests corrupts some downloads. | ||
| Description |
I tried this on 2 seperare XP Pro VirtualBox VMs, the first was using XP SP3 RC2.
Summary of Testing:
Downloads would appear to complete successfully but when run I would receive "Setup file corrupt" type messages during installation. I eliminated SP3 as a possability through rolling back to a pre-sp3-install snapshot - no luck. I tried a 2nd VirtualBox virtual machine with a base install of XP Pro SP2 (no updates or apps of any kind installed after XP Pro install - used for testing our installation packages) with the same results. I tried downloading and installing the same files (to eliminate the unlikely possability that the actual distributions WERE corrupt to start)on an XP VM on one of our ESX servers and had no issues. I tried changing my host NIC and ended up using all three (listed above) to no avail.
One thing to mention - and I will verify this tongiht - I was not seeing this issue when connected to my home network. I connect directly to a common internet gateway\modem device using NAT at home, at work we use Routing and Remote Access on a Win2K3 Server as a NAT Gateway. I marked this incident as minor because I was able to resolve my issue by switching to "Host interface" and setting up a bridge to the Kensington Port-Rep adapter. It's inconvenient however for moving the VM among various hosts within my develpoment workspace, where NAT just transparently works when a VM is moved. |
|||

