Bug 104654

Worked fine for me - I installed on x86-64 this morning (stable autobuild tree).

So what exact versions of hwinfo and yast2-core did you use? 

After some debugging we have found that it depends on the "D-BUS daemon".

When the D-BUS is running, probing doesn't work, when we shut it down, it starts
to work.

How to reproduce:
rcdbus stop
rcdbus status
echo "\`Read(.probe.disk)" | /usr/lib/YaST2/bin/y2base stdio scr
/ works /

rcdbus stop
rcdbus status
echo "\`Read(.probe.disk)" | /usr/lib/YaST2/bin/y2base stdio scr
/ doesn't work /

I can provide all strace logs but.... it is a lot of data :)))) and easy to
reproduce (with stable) or with Beta1 with new hwinfo installed (both works that
way).

er, sorry

the second is:
... rcdbus start

;)

Hm, works fine for me in both cases. You might try the latest hwinfo from 
/work/built/mbuild/ligeti-snwint-4/ 

BTW, does 'hwinfo --disk' work? 

Yes, hwinfo --disk works well. ... or returns something I'd expect as an output :)))
Please, try it on root@liche.suse.cz

I see no problems on my test machines. Maybe your yast was compiled against  
a different libhd version?  

My YaST have been installed from SUSE Linux 10.0 Beta1 DVD ISO image.
(Clear installaton today)
The only difference is the hwinfo[-devel] installed from our synchornized /work.

STABLE installation testing was reproduced on Stano's and my computer. Well,
using the same source. I'll try it tomorrow again. On the other hand, you should
have seen the liche.suse.cz's system (still available). yast2-core hasn't been
reinstalled.

The D-BUS problem has been found by Martin and me by diffing the strace logs
with standard Beta1 against `today`'s STABLE.

I just tried it with the full tree created overnight. 
Again, YaST does not detect any disks. 
However, running "hwinfo --disk" from cmdline finds the disk. Also running 
SCR::Read(.probe.disk) from cmdline reports the disk correctly. 
 
Puzzling. Will attach y2log. 

Created attachment 46138 [details]
y2log

Arvin, Thomas, there is a wrong array index mentioned at line 584: 
StorageDevices.ycp:198 invalid index 0 (max -1) in YCPValue 
YCPListRep::value(int) const 

Adrian just experienced the same with his laptop. 

The kernel detected the disk, see attached boot.msg  

Created attachment 46139 [details]
boot.msg

Bug #104715 is probably related. 

The invalid index is not the cause of the problem.  The SCR simply
returns nothing.  This is the code in StorageDevices.ycp

    list<map> all_disks = (list<map>) SCR::Read(.probe.disk);
    y2milestone( "localProbe: disks probed");
    y2milestone( "localProbe: all_disks %1", all_disks );

And the log says:

    localProbe: all_disks []

Bug #104715 seems to cause this bug, marking as duplicate.

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

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

Just for information the invalid index mentioned by Klaus was due to the
fact that no cdrom was detected at all. 
This had no consequences at all but of course it is meanwhile fixed.

How does libstorage react if no disks are found ? 
(I'm currently experiencing YaST crashes if no disks are found) 

libstorage should not crash.
Here I get disks detected and my YaST2 crashes also with current Beta#2 instsys.

hal now works and yast never finds disks 

I think I've found it 

seems to work. fixed in libhd 11.12