Hi, basically the amd64 liveDVD works fine for me but lets spot few error I see. I suspect crappy glibc causing hald and other apps to crash. This is current bootup so I show only hald crash but I saw other apps crash as well. There is some error I ignore in the console complaining about splash image not accessible or something like that. I do not have the message available anymore although it is probably reproducible. The message appears at the very end of bootup process just around the X server starting. I could dig uop more in this and open anothe bug, in case you want. # dmesg [cut] r8169: eth1: link up eth1: no IPv6 routers present ADDRCONF(NETDEV_UP): eth0: link is not ready sda: sda1 sdb: sdb1 sdb2 md: nonpersistent superblock ... md: bind<sda> md: nonpersistent superblock ... md: bind<sdb> raid1: raid set md0 active with 2 out of 2 mirrors md: resync of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. md: using 128k window, over a total of 78150744 blocks. md0: detected capacity change from 0 to 80026361856 md0: p1 hald[6812]: segfault at 0 ip 00000000004376a5 sp 00007fffe76b48b0 error 4 in hald[400000+58000] md: md_do_sync() got signal ... exiting md: checkpointing resync of md0. md: md0 stopped. md: unbind<sdb> md: export_rdev(sdb) md: unbind<sda> md: export_rdev(sda) md: md127 has zero or unknown size, marking faulty! md: error, md_import_device() returned -22 md: md0 stopped. sdb: sdb1 sdb2 sdb: sdb1 sdb2 sdb: sdb1 sdb2 sdb: sdb1 sdb2 sdb: sdb1 sdb2 sda: sda1 md: bind<sda1> md: bind<sdb1> md: md0: raid array is not clean -- starting background reconstruction raid1: raid set md0 active with 2 out of 2 mirrors md: resync of RAID array md0 md: minimum _guaranteed_ speed: 1000 KB/sec/disk. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. md: using 128k window, over a total of 78148096 blocks. md0: detected capacity change from 0 to 80023650304 md0: unknown partition table md0: p1 md: md0: resync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sda1 disk 1, wo:0, o:1, dev:sdb1 md: md1 stopped. md: md1 stopped. md: bind<sdd1> md: bind<sde1> md: bind<sdf1> md: bind<sdc1> raid10: raid set md1 active with 4 out of 4 devices md1: unknown partition table kjournald starting. Commit interval 5 seconds EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with writeback data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on md1, internal journal EXT3-fs: mounted filesystem with writeback data mode.
Reassigning this bug to the ten team. As hal has been dropped in the latest Xorg releases, this can probably be closed as OBSOLETE.
Please test the latest 11.1; http://torrents.gentoo.org/?category=11.1 thanks
hald on the livedvd should not be started by any of the services and the issue with splash and the read-only doesn't affect functionality at all. This bug can be closed as HAL will no longer be included on the livedvd but if you can provide the names of the programs which fail to start because of hald, please let us know here.
Closing.
