the panel of the desktop can't showup.

Please see below image:
http://pic.yupoo.com/hoohoobjj/483128fbd007/ycd7kw8c.png

today, I start my computer, got some filesystem error, prompt message ask me to run fsck manually, and I did so, then I can login my system, but the panel of the desktop can’t showup.

How can I get back my panel?

and when I run yast2 on command line, I got below messages:

** (y2controlcenter-gnome:6552): WARNING **: error accessing /apps/yast-control-center/cc_actions_list [Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)]

** (y2controlcenter-gnome:6552): WARNING **: key not found [/apps/yast-control-center/cc_actions_list]

Loading simple Config module …
Creating backend …
Reading pinyin phrase lib failed
Loading socket FrontEnd module …
Starting SCIM as daemon …
Loading socket Config module …
Creating backend …
Loading x11 FrontEnd module …
Failed to load x11 FrontEnd module.

If you had to run fsck then you file system was corrupted. Though that will fix the file system you man not recover all the files. You can find the pieces that th program did not know how to handle in the lost & found directory.

Which desktop and what partition did you have to repair?

:shame::shame:how can I check these information? (Which desktop and what partition???),

below is some information in /var/logs/messages:

Mar 11 10:31:38 linux-7dqw kernel: 114.293898] FAT: Filesystem error (dev sdc6)
Mar 11 10:31:38 linux-7dqw kernel: 114.293907] fat_get_cluster: invalid cluster chain (i_pos 0)
Mar 11 10:31:38 linux-7dqw kernel: 114.293914] File system has been set read-only
Mar 11 10:31:38 linux-7dqw kernel: 114.305283] FAT: Filesystem error (dev sdc6)
Mar 11 10:31:38 linux-7dqw kernel: 114.305300] fat_get_cluster: invalid cluster chain (i_pos 0)
Mar 11 10:31:38 linux-7dqw kernel: 114.305680] FAT: Filesystem error (dev sdc6)
Mar 11 10:31:38 linux-7dqw kernel: 114.305688] fat_get_cluster: invalid cluster chain (i_pos 0)
Mar 11 10:34:37 linux-7dqw kernel: imklog 4.4.1, log source = /proc/kmsg started.
Mar 11 10:34:37 linux-7dqw kernel: 31.692064] ip6_tables: (C) 2000-2006 Netfilter Core Team
Mar 11 10:34:37 linux-7dqw kernel: 31.850636] ip_tables: (C) 2000-2006 Netfilter Core Team
Mar 11 10:34:37 linux-7dqw kernel: 31.890935] nf_conntrack version 0.5.0 (7980 buckets, 31920 max)
Mar 11 10:34:37 linux-7dqw rsyslogd: [origin software=“rsyslogd” swVersion=“4.4.1” x-pid=“1099” x-info=“http://www.rsyslog.com”] (re)start
Mar 11 10:34:37 linux-7dqw SuSEfirewall2: batch committing…
Mar 11 10:34:38 linux-7dqw SuSEfirewall2: Firewall rules set to CLOSE.
Mar 11 10:34:44 linux-7dqw kernel: 38.170381] powernow-k8: Found 1 AMD Athlon™ 64 Processor 3000+ processors (1 cpu cores) (version 2.20.00)
Mar 11 10:34:44 linux-7dqw kernel: 38.170450] powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x6
Mar 11 10:34:44 linux-7dqw kernel: 38.170456] powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x12
Mar 11 10:34:45 linux-7dqw kernel: 39.184028] Clocksource tsc unstable (delta = -139598884 ns)
Mar 11 10:34:49 linux-7dqw gdm-simple-greeter[1427]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion G_TYPE_IS_FLAGS (flags_type)' failed Mar 11 10:34:49 linux-7dqw gdm-simple-greeter[1427]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion G_IS_PARAM_SPEC (pspec)’ failed
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Sucessfully called chroot.
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Sucessfully dropped privileges.
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Sucessfully limited resources.
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Canary thread running.
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Failed to make ourselves RT: Invalid argument
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Watchdog thread running.
Mar 11 10:34:50 linux-7dqw rtkit-daemon[1442]: Running.
Mar 11 10:34:50 linux-7dqw gdm-simple-greeter[1427]: WARNING: could not find item with id ‘__auto’ to remove timer
Mar 11 10:34:51 linux-7dqw pulseaudio[1440]: pid.c: Stale PID file, overwriting.
Mar 11 10:34:52 linux-7dqw pulseaudio[1440]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-SBBLtOa7Zw: Connection refused

Ok you ran fsck so which partition did you run it on? Was it the root or home?

Are you running KDE or Gnome?

Note it looks to me as if you are having hardware problems. But answer the above first

I didn’t indicate partition when I run fsck, I only press “fsck” on the command line.

it should be gnome.

Didn’t gnome users have a issue with Cario that messed up the Panel?

Guess you could always create a new user account and see if it has the same issue.

I tried to login using root user, the panel can shown up correctly.
how can I fix this problem for that user?

Please login via console, like this:
http://public.bay.livefilestore.com/y1pCG5Cj_cWBaELzNbmygijNGrTruTkqtI3DpqUTUFfGhQW0kV0wmfgr40FaYF_XEgpzoeU5PzMp0-JzA0lkWyFZw/console.login.png

Just enter your username and then password

once logged in type: su (then hit enter)
type your root password

you should now be su
Now type the following:

zypper ref

then

zypper up

If it updates some stuff, when it’s done, type:

reboot

Has this made any difference?

I did above steps and reboot, no difference.

I don’t use gnome but try this:
Login as before with the console:

No need to be root this time, do these:

mv .config .gonfig-old
mv .gconf .gconf-old
mv .gconfd .gconfd-old
mv .gnome2 .gnome2-old

when done, type: startx

Another alternative to try is create a new user account and try logging in to that as a normal user.
Tell us what happens

NEVER EVER LOGIN ON A DESKTOP AS ROOT !!! Caf suggested to create a new user. If things work well as that new user, it brings down things to a level of user’s configuration.

Did fschk do anything? ie did it show the fix happening? With out any parameters it only does a check and does not fix anything. See man fsck So a good possibility he file system errors still exist.

after above steps, the panel is back!! lol!lol!, thank you!

my old user’s panel is back now, but I still tried to create a new user(username: test) to login, but got problems:

pop up a alert said:
Could not update ICEauthority file /home/test/.ICEauthority.

pop up another alert said:
There is a problem with the configuration server.(/usr/lib/Gconf/2/gconf-sanity-check-2 exited with status 256)

and then pop up another alert said:
Nautilus could not create the following required folders:/home/test/Desktop. /home/test/.nautilus.
Before running Nautilus, please create these folders. or set permisstions such that Nautilus can create them.

and then I got a desktop with nothing. >:(>:(>:(

something wrong with my configuration server? how can I fix this? how can I give permisstion to Nautilus?

I remember a lot of messages when running fsck, I said “yes” for any question, seems have “fix” something.

I am reading man page for fsck now, will look into the filesystem issue later, thanks for your advice:)

You should never run with a corrupted file system. It can cause irretrievable data loss.

I agree with gogalthorp. In most cases a filesystem being obviously heavily corrupted means at least having to play back a backup of the respective partition. To me it looks like both your /- and /home-partition have been harmed.

Corrupted filesystems often (although not always) are caused by damaged blocks and sectors on the hardrive itself. I would check this, for example via s.m.a.r.t. or tools which are usually offered by the manufacturer of the hd. I recommend the “Hitachi Drive Fitness Test”, which runs on many different brands (not only Hitachis or Samsungs). These tools are able to actually fix damaged sectors to some degree. After the hd has been checked and (successfully) fixed, use the backup you hopefully have in store or reinstall.