Custom Query (16363 matches)
Results (151 - 153 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1890 | obsolete | VBoxHeadless does not set the user correctly when run from SysV init script | ||
| Description |
I'm starting a VM from a Ubuntu init script which uses the helper program start-stop-daemon. Although I used the --chuid user option, the resulting instance of VBoxHeadless does not appear to know the username. In particular this affects the VBoxXPCOMIPCD service which created a directory called /tmp/.vbox--ipc (notice the empty string between the hyphens, normally when VBoxHeadless is started from a terminal, the directory is /tmp/.vbox-user-ipc). This means that VBoxManage cannot find the instance of the VM to send IPC to, for example, to send Ctrl-Alt-Del scancodes. Setting LOGNAME to the intended username seems to fix this, as in: LOGNAME=user start-stop-daemon ... The correct fix would be for the service to check its uid and map it back to the username. |
|||
| #1908 | obsolete | VirtualBox mute on alsa/dmix configuration | ||
| Description |
dmix is an alsa plugin for user space sound stream mixing. The problem is that when the "default" alsa audio device is routed through dmix, then applications that try to open "default" for recording fail as dmix is only an output plugin. In general, the trick is to set the input device to something besides from "default" for these applications ("null"/"hw:0,0" is an option). This is possible with VirtualBox by setting the VBOX_ALSA_ADC_DEV=".." variable. First suggestion: Replacing the error message 00:00:08.982 ALSA: Failed to open 'default' as ADC with something like 00:00:08.982 ALSA: Failed to open 'default' as ADC, set VBOX_ALSA_ADC_DEV environment variable. in alsaaudio.c. I had to read "audio_process_options/audio_get_conf_in" in audio.c closely to understand what the code is actually doing. Second suggestion: If the input device is unavailable, complain but don't go mute completely. I presume the user rarely cares about a working input stream but will most certainly care about a working output stream. The strategy for alsaaudio.c in alsa_init_in could be: call alsa_open for a second time but with "null" set as conf.pcm_name_in. |
|||
| #1920 | obsolete | Windows Mobile (RNDIS) USB device NOT WORKING BY DEFAULT | ||
| Description |
I have an issue with connecting my Windows Mobile device to the Guest OS (Windows XP SP2). Host is Ubuntu Linux 8.04. The device is an HTC Mogul (PPC-6800). The device appears as "HTC Generic RNDIS". The actual "symptoms" inside the Guest vary... sometimes the device shows up in Hardware Manager (as "Windows-mobile network adapter"). Other times it doesn't show up at all, and other times it shows up with a red icon next to it indicating a problem status. In no cases will ActiveSync ever recognize that you have a mobile device plugged in. All other USB devices that I've tried work fine inside the Guest. MY WORKAROUND: To make it work I have to make one setting change on the PDA itself. Go to Settings -> Connections -> USB to PC. UNCHECK the box that says "Enable advanced network functionality". My device sometimes hangs trying to apply this setting.. if so use the soft reset hardware button, then try again. This setting totally changes how the device behaves on the USB bus.. it now appears as "HTC Generic Serial" and with different USB IDs, etc, and it uses different protocols to communicate with the Host Adapter (it's a lot of black magic I don't know too much about). This issues really does need to be resolved somehow, as I actually want to be able to use the "advanced network functionality" that my PDA has to offer. I'm happy to assist in debugging and development, including remote access to systems where you can access my device if that would be of any assistance. I've attached the output of two commands to this ticket. "VBoxManage list usbhost" and "lsusb". |
|||

