> > 1. I tried to burn the .iso image to a CD but it > wouldn't fit. I used > > "cdrw -i <iso_file>". Writer is a NEC-3550A > CD/DVD writer. Output was: > > > > # cdrw -i 0805rc2a.iso: > > Looking for CD devices... > > Initializing device...done. > > Size required (719120384 bytes) is greater than > available space (681986048 bytes > > ). > > > Since we are pushing the size limits, you need to use > the -C option. > i.e. cdrw -C -i 0805rc2a.iso.
Yes, several people told me this. Thanks for the info. Should possibly be the default as suggested by others. > > 2. The install seemed slower than in preview 2 but > I didn't time it. > > But the map for timezone selection is nice. The > installation went smoothly. > > Something I did during the install created a > core file. Mdb showed the > > stack trace to be: > > > > ::stack > > 0xfa3df32c(84469b0) > > > libxpcom_core.so`__1cNnsCOMPtr_baseSassign_with_AddRef > 6MpnLnsISupports__v_+0x38( > > 83e7710, 0) > > > libxpcom_core.so`__1cSfactory_ClearEntry6FpnMPLDHashTa > ble_pnPPLDHashEntryHdr__v_ > > +0x35(80f7bc8, 80f9e28) > > libxpcom_core.so`PL_DHashTableFinish+0x5f(80f7bc8) > > > libxpcom_core.so`__1cWnsComponentManagerImplIShutdown6 > M_I_+0x8d(80f7ba0) > > libxpcom_core.so`NS_ShutdownXPCOM_P+0x193(0) > > libxpcom.so`NS_ShutdownXPCOM+0x1b(0) > > libgtkembedmoz.so`NS_TermEmbedding+0x4d(80f0c88, > 80b80a0, fa3df328, 8066d19, 804 > > 79e8, fa3beddc) > > > libgtkembedmoz.so`__1cMEmbedPrivateKPopStartup6F_v_+0x > a7(80be458, 80479f8, feffd > > e48, 80479f8, 8066d19, c70) > > > libgtkembedmoz.so`gtk_moz_embed_pop_startup+0x18(c70, > 806e5a4, 8047a0c, 80675eb, > > 0, 86bc670) > > yelp_gecko_shutdown+0x29(0, 86bc670, feffde48, > 8047aec, 806e5a9, 8047ba8) > > yelp_html_shutdown+0xb(8047ba8, 8047ad4, feffb7cc, > 8047a38, fefd36c9, feffde48) > > main+0x525(2, 8047b18, 8047b24) > > _start+0x7a(2, 8047c10, 8047c1b, 0, 8047c4a, > 8047c7e) > > > Could you please file a bug against this. The > category would be desktop. I filed bug 1669, which is now reproducible by running Device Driver Utility, clicking on Help, closing DDU window, then closing Help window. > > 4. After entering username and password at the > login screen, the desktop > > background remains black for awhile. During > this time, I can hear the > > floppy drive being accessed and the light for it > is also on (there is > > no floppy in the drive). After perhaps 20-30 > seconds this stops and then > > the desktop background appears. > > > Does this occur the first time after install or does > it occur everytime ? It occurs every time I login the first time after boot, but only if I login too soon after desktop login screen appears. If I wait about 1 minutes after login screen appears and then login, the problem does not occur. > > 5. After the desktop background appears, the top > panel is still blank. > > It stays blank for many minutes. Running prstat > shows that gnome-panel is > > using one whole CPU. Killing gnome-panel causes > the top panel menu items > > etc to appear as expected and then everything > works fine. I ran truss > > and attached it to the process and it looks like > it is repeating the same > > sequence of calls with a small number of files > (mostly access, open64, > > fstat64, read and close calls). I can provide a > section of the truss > > output if this is not a known issue and if it > would be useful. > > > Check if a bug has been filed. I have not seen this > issue reported so > it may be new. I have filed bug 1681. This problem also only occurs on first login after boot and also only if I login right away after desktop login screen appears. Again, waiting a minute or so before logging in prevents the problem from occurring. I disconnected my floppy drive but it didn't make any difference. -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
