Custom Query (16363 matches)
Results (1219 - 1221 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13067 | obsolete | Battery Drain when lid of MacBook Air is closed | ||
| Description |
After about 3 hours of sleep a heavy battery drain starts on MacBook Air (MacOS 10.9.3) when running VB with Windows 7 installed. syslog | grep -i "Wake reason" shows May 23 11:37:48 NAME kernel[0] <Debug>: Wake reason: ? May 23 11:38:30 NAME kernel[0] <Debug>: Wake reason: ? May 23 11:39:08 NAME kernel[0] <Debug>: Wake reason: ? May 23 11:39:57 NAME kernel[0] <Debug>: Wake reason: ? ... one entry every minute until battery is empty. |
|||
| #388 | obsolete | BeOS 5 stucks on boot | ||
| Description |
BeOS 5 stucks on graphical boot. There is graphical image being displayed, but it has no reactions and no DVD/HDD activity. Tested on: Vista, VBox 1.4.0 |
|||
| #6574 | fixed | Behavioral extension of remove machine action | ||
| Description |
When creating a new machine a file for the disk is also created. However when removing a machine that disk file is left untouched. This has two effects which strikes me as less than awesome:
However I got told on IRC that it wasn't quite that easy. A machine could be using multiple disks and removing them just because you removed a machine is absolutely not what you want. My first thought was to add a three way dialog when removing a machine:
But maybe you want to save some disks and remove some disks someone then said. It is probable too complicated to have a huge dialog where you can choose to delete some and keep some. (Although Eclipse does something similar regarding what to save and not to save when closing all editors at once) Anyway, I think my issues boils down the fact that deleting a machine is not the opposite action of creating one. But the names hint at it and the vdi files which get's left behind does so silently. Maybe someone else can think of a nice solution to this problem? |
|||

