If anyone's still having trouble with their clock, I may have found a solution. Although I didn't have the moving / unlocking issue, I couldn't add my clock. I got an unhelpful message about an error with OAFIID:GNOME_ClockApplet. My ~/.xsession-errors log contained:
** (gnome-panel:1521): WARNING **: panel-applet-frame.c:1273: failed to load applet OAFIID:GNOME_ClockApplet:
System exception: IDL:Bonobo/GeneralError:1.0 : Child process did not give an error message, unknown failure occurred
Specifically, the last post on that page (from Feb 2) showed that I was missing libedataserver-1.2.so.11. I checked in synaptic, and this had been upgraded to libedataserver-1.2.so.12.
The solution was to `cd /usr/lib` and then run `sudo ln -s libedataserver-1.2.so.12 libedataserver-1.2.so.11`. Hope this helps somebody!
If anyone's still having trouble with their clock, I may have found a solution. Although I didn't have the moving / unlocking issue, I couldn't add my clock. I got an unhelpful message about an error with OAFIID: GNOME_ClockAppl et. My ~/.xsession-errors log contained:
** (gnome-panel:1521): WARNING **: panel-applet- frame.c: 1273: failed to load applet OAFIID: GNOME_ClockAppl et: GeneralError: 1.0 : Child process did not give an error message, unknown failure occurred
System exception: IDL:Bonobo/
I found this site, which helped: http:// www.linuxforums .org/forum/ suse-linux- help/57382- oafiid- gnome_clockappl et.html
Specifically, the last post on that page (from Feb 2) showed that I was missing libedataserver- 1.2.so. 11. I checked in synaptic, and this had been upgraded to libedataserver- 1.2.so. 12.
The solution was to `cd /usr/lib` and then run `sudo ln -s libedataserver- 1.2.so. 12 libedataserver- 1.2.so. 11`. Hope this helps somebody!