[SOLVED] Desktop won't load 2.0

[bikefreak]

Been using 2.0 for since it came out (1.0 before that) and have not had any significant problems until yesterday. I was running firefox, downloaded picture to desktop. Went to open picture and received an error about something failing. Thinking this is the graphics program crashing I click cancel or ok vs "sending error to Mageia?" Also didn't pay sufficent attention to the error as I figured it just crashed and a reboot would solve my problems. not so much.

After rebooting I was left with my background and nothing more. the desktop never loaded (icons) and the "start menu/bar" never loaded. Everything else is working fine. I can run anything from guake (command line) and it comes up just fine. Firefox works, updates work, etc. mouse works. I can right click to login/logout. "Desktop" button (upper right) is there and working.

Did a full evening of google searching and have not found any leads on how to fix this or where to look. Well I did find /var/log/messages but didn't see anything in there I could associate with my problem.

edit*

Code: Select all

dmesg |grep -i failed
[    0.463501]  pci0000:ff: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
[    0.468745]  pci0000:00: ACPI _OSC request failed (AE_SUPPORT), returned control mask: 0x0d
[   19.159855] hdaps: driver init failed (ret=-19)!
[   19.265537] iTCO_wdt: probe of iTCO_wdt failed with error -16

So faithful Mageia community, where do I go from here?

thanks so much.

-dave

~message edited by moderator; terminal-output placed between [CODE/CODE]-tags

[filip]

Your HD might be failing. I would definitely check HD SMART state and at least do a quick test with GSmartControl which is available in MCC.

[bikefreak]

Running GSmartControl.... Results posted in 3 hours after I get home to see results.

[doktor5000]

Apart from that, it would have been good if you would have captured the exact error message/crash, as otherwise it's nearly impossible to tell what went wrong and how to fix your exact problem. But as you seem to be using KDE, best bet is to logout, start a text login and move away/rename your

Code: Select all

/home/username/.kde4/

But which desktop are you using currently?

[bikefreak]

KDE4. I know I'm a bonehead for not reading the error. (been too conditioned to application failures that clear up after crash or reboot.) lesson learned.

After rename of .kde4 what happens? (I assume cross fingers and reboot)

[doktor5000]

After rename of .kde4 what happens? (I assume cross fingers and reboot)

It creates new, clean default settings for the whole of KDE, this is also often required for major KDE updates or at least partially, depending on how much your configuration differs from the default settings. And reboot is not required, just login as your user afterwards normally and you should be good to go.
But you can still cross your fingers and hope for the best

[bikefreak]

Sounding like my best bet. I'm going to wager that doing this will resolve the problem. I'll check it out in an hour when I get home. Thanks for the help!

[bikefreak]

HD scan came back clean.

Moving the .kde4 directory worked. Thanks so much for the help.