| Summary: | app-emulation/virtualbox-1.3.4 hard reset under amd64 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alessio Cassibba (X-Drum) <swapon> |
| Component: | New packages | Assignee: | AMD64 Project <amd64> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | CC: | jokey, swapon |
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Alessio Cassibba (X-Drum)
2007-02-15 10:51:45 UTC
I think masking it temporarily should be the way to go until the issue is solved. amd64: your thoughts? give me a day to reproduce it first (In reply to comment #2) > give me a day to reproduce it first > sometimes it occurs during the installation of an application or on automatic system updates (sorry for previous comment: mistake) Okay, I didn't realize this package provided a kernel module, so a hard-lock isn't all that special. Upstream's homepage says: * A supported host operating system. Presently, we support 32-bit Windows (primarily XP) and many Linux distributions. Support for Mac OS X and 64-bit operating systems is currently in the works. I marked it -amd64. We'll happily reconsider keywording it once upstream supports 64bit OSes too. Upstream fixed this, please re-keyword the live ebuild Done. Do you want to keep this bug open or close it and reopen it once a new version is out? A little update about the hard reset problem on amd64,
the problem still occurs in:
app-emulation/virtualbox-{1.3.4, 1.3.6, 1.3.8}
app-emulation/virtualbox-bin-{1.3.4, 1.3.6, 1.3.8}
the only version not affected is the svn version,
with the last 1.3.8 the problem still occurs.
Upstream will implement it in 1.4 (talked to them about it today) |
