I have not been able to load Rawhide on my office computer for several days now. Just after one acknowledges that one is installing test software, an unhandled exception stops the storage devices discovery.
I can't give the traceback because the save option immediately calls the find storage devices routine.
This is with a Gigabyte ga-ep45-ud3p and Core Duo cpu, 4GB ram and sata drive with a mixture of NTFS and Linux partitions.
I also get this issue with a PATA drive 720GB Formatted to EXT4 from fedora preview. I also can't install over an EXT3 partition 120GB PATA Both Western Digital
On Mon, Jun 15, 2009 at 7:24 PM, Chuck Forsberg WA7KGX N2469R caf@omen.comwrote:
I have not been able to load Rawhide on my office computer for several days now. Just after one acknowledges that one is installing test software, an unhandled exception stops the storage devices discovery.
I can't give the traceback because the save option immediately calls the find storage devices routine.
This is with a Gigabyte ga-ep45-ud3p and Core Duo cpu, 4GB ram and sata drive with a mixture of NTFS and Linux partitions.
-- Chuck Forsberg caf@omen.com www.omen.com 503-614-0430 Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 FAX 629-0665
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On 06/15/2009 02:24 PM, Chuck Forsberg WA7KGX N2469R wrote:
I have not been able to load Rawhide on my office computer for several days now. Just after one acknowledges that one is installing test software, an unhandled exception stops the storage devices discovery.
I can't give the traceback because the save option immediately calls the find storage devices routine.
This is with a Gigabyte ga-ep45-ud3p and Core Duo cpu, 4GB ram and sata drive with a mixture of NTFS and Linux partitions.
Bug 497240 - anaconda loops endlessly when trying to save traceback
check tty-3 and see if there is an additional (newer?) traceback not related to the original.