Custom Query (16363 matches)
Results (1243 - 1245 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1271 | worksforme | No link to bugtracker from virtualbox.org | ||
| Description |
A link to the bug tracker should be added to the virtualbox website so that users can report bugs. To find the bug tracker I had to use google; I tried using the in-site search engine and could only located currently created bugs. Maybe add something under Contribute or the main menu? |
|||
| #1272 | invalid | Can not install Virtual box on Ubuntu 7.10 "Gutsy Gibbon"... | ||
| Description |
I have added repositories according to www.virtualbox.org and that's ok so far. Now trying to install:
Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies:
E: Broken packages A quick search with Google reveals that libqt3c102-mt is replaced by libqt3-mt:
Reading package lists... Done Building dependency tree Reading state information... Done Package libqt3c102-mt is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it:
E: Package libqt3c102-mt has no installation candidate I have libqt3-mt installed but this does not help. Also the libssl0.9.7 is replaced by libssl0.9.8 which I also have installed. So this means that I am unable to install Virtualbox. I guess the easiest solution is to regenerate the package pointing to the new libs, but that I can't do... |
|||
| #1273 | fixed | serial ports problem | ||
| Description |
I am using VirtualBox 1.5.6 (VirtualBox_1.5.6-1_Win_x86.msi) on Windows XP. Guest system is Windows Server 2003 from en_windows_server_2003_with_sp1_enterprise.iso (MSDN). I configured virtual machine to have com port on Host Pipe, but it doesn't seem to work. When I look at guest's Device Manager, it shows no ports at all; when I look at its Resources view, it doesn't show serial port resources as used (standard COM1). I added COM2 to use physical port, and result is the same. On the other hand, when I run Process Explorer on host, it shows both handles as open by VirtualBox process. So, the question is: how to have serial ports work? I really need only pipe (to connect WinDbg). |
|||

