Bug 467885

Summary: Installation fails after agreeing to Beta Relase Notification
Product: [Fedora] Fedora Reporter: John Love <twosinners>
Component: halAssignee: Richard Hughes <richard>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dcantrell, pertusus, rhughes, richard
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-21 15:22:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Debug output of failed install none

Description John Love 2008-10-21 14:29:08 UTC
Created attachment 321018 [details]
Debug output of failed install

Description of problem:
 After clicking the agree to Beta Relase notification an Install error with Description, DEBUG, etc. prompts.  If I choose Debug, I get a lot of output but the relevant line is this:
ValueError: Invalid object path '/org/freedesktop/Hal/devices/storage_model_SAMSUNG_HD080HJ/': ends with '/' and is not just '/'

I plugged in a different hard drive and it continued past this to the Disk format warning dialog box.

Version-Release number of selected component (if applicable): 
FC10 Beta Relase


How reproducible: 
Using the Samsung Hard Drive in my Dell GX620 it will fail each time I try to install.


Steps to Reproduce:
1. Insert DVD
2. Boot
3. Click Install/continue
4. Click English US Localization
5. Click English US Keyboard
6. Click the I agree it's Beta Software button
Crash
  
Actual results:
Will not continue to install.

Expected results:
Will install successfully

Additional info:
I tried a second hard drive (Segate) that seemed to work properly.  It seems related only to the Samsung drive that came with the GX620.

Comment 1 Richard Hughes 2008-10-21 15:22:11 UTC

*** This bug has been marked as a duplicate of bug 442457 ***