Crash Boom Bang

[TRN]

I just finished installing MDK rc2 and while the openings got my attention, choosing the Bookmarks link to OSNews.com provided this error message:

The application KDE Panel crashed and caused the signal 11.

OK. So, you see they link to OSNews and even OfB.biz but not PCLinuxOnline nor TuxReports ...

Drats. I can understand leaving us out but why not PCLO? Maybe we should suggest to them that it gets put in as a bookmark.

[TRN]

So far, the only thing I've received from this MDK 9.1 rc2 installation is crash after crash. I just went into GNOME and clicked on the link to Documentation and BOOM

Application "galeon-bin" (process 1945) has crashed due to a fatal error

Gesh, this isnt' good. It is a rc2 for goodness sakes. I didn't have any of these problems with the rc1.

[TRN]

I tried another clean installation and it also failed.

i815 chipset system
30 GB drive AT -100
DVD drive
986FS monitor
Logitch mouse
Microsoft keyboard

Same failures as noted above -- and should also state that none of the applications were available in the menu.

[robbie_n]

Did you do the usual md5sum check?

Try reburning at a lower speed to make sure you haven't got a bad burn.

[NinerFan]

LPH,

You mentioned not having as many problems with rc1, but is this the exact same hardware you ran rc1 on?

Also, in your hardware specs, I didn't see what type of CPU and memory you have.

Also, what manufacturer of hard drive do you have? I know a guy that works Mandrake tech support, and I remember him saying one time a few months ago, that Mandrake and Western Digital drives don't mix. He said they have no idea why, but whenever they have someone with a bunch of problems, it is someone that has a WD drive. And whenever that person switched to a non-WD drive (all other hardware exactly the same) then the problems went away.

Finally, I would check your memory. There is a great tool called Memtest86 which I highly recommend. You can find it here: http://www.memtest86.com/ .
Create a bootdisk of this one and keep it in your inventory. This tool has been the saving grace of a lot of problems for both Linux and Windows installations.

Good luck!

[TRN]

LPH,

You mentioned not having as many problems with rc1, but is this the exact same hardware you ran rc1 on?

Also, in your hardware specs, I didn't see what type of CPU and memory you have.

Also, what manufacturer of hard drive do you have? I know a guy that works Mandrake tech support, and I remember him saying one time a few months ago, that Mandrake and Western Digital drives don't mix. He said they have no idea why, but whenever they have someone with a bunch of problems, it is someone that has a WD drive. And whenever that person switched to a non-WD drive (all other hardware exactly the same) then the problems went away.

Finally, I would check your memory. There is a great tool called Memtest86 which I highly recommend. You can find it here: http://www.memtest86.com/ .
Create a bootdisk of this one and keep it in your inventory. This tool has been the saving grace of a lot of problems for both Linux and Windows installations.

Good luck!

Thanks. I know I'm being lazy by not putting in all the details. This system was exactly the same as rc1 install. Actually this system has had so many previous mandrake versions and betas that it isn't hardware. It had MDK solely on it for many years.

Celeron 800 MHz, 128 MB PC133 DRAM, WD 300BB-00AUA1 hard drive.

JAMD is on it right now. Libranet 2.8 beta was previously on it. Installation options were not recorded on paper at the time I did the install but there may be an issue to look into before they ship 9.1. I've been able to recreate the problem on the system so now it is a matter of getting it installed by default and then tracing it back.

I should say that it is best to completely wipe out partitions etc for a MDK install -- otherwise -- I've seen this problem many many times moving between distros (usually ext3 and ReiserFS) -- oh well.

I'll let everyone know but tonight I'm just being lazy :)

UPDATE: I noticed that I didn't answer robbie_n regarding the md5sum. Yes, they were checked and all is well.

[TRN]

OK, this is how I fixed things.

No matter how I installed this rc2, the opening KDE menu was broken. Therefore, I immediately used Mini-CLI (ALT-F2) and typed mcc. Then I entered MenuDrake and asked for the system to be updated. This fixed the menu.

OpenOffice, KWord, Konqueror, TuxRacer and Frozen bubble, gimp all seem to be fine. After fixing the menu the link to OSNews works too. However, Mozilla and galeon still crash.

LinNeighborhood found the Libranet and Lindows boxes just fine.

:roll:

[TRN]

So these are the four packages with problems during the install

xine-plugins-1.0beta4.1mdk.i586
xmms-skins-1.0.0-13mdk.noarch
xine-ui-0.9.18-1mdk.i586
xlockmore-5.0.5-4mdk.i586