Mikus Grinbergs wrote:
Have now experienced similar problems with three different systems (two 10.0, one 10.1). I'm surprised that my quick look around has found no solutions - I doubt that I am the only one seeing this.
I'm somebody who normally downloads new versions as soon as they become available in often-subscribed-to repositories (e.g., gnome). When I first installed my systems, I did not have a problem. Chances are that the "panel not responding" problem arose from an upgrade somewhere - but I don't know which, nor whether the recent kernel upgrade I did has made things worse.
Symptom: Clicking the mouse while the cursor is anywhere on the gnome panel does not cause anything to happen. (Where I've defined both a top and a bottom panel, the same lack of response happens with either.) 'killall gnome-panel' redraws the panel(s), but does not affect the non-responsiveness. On a panel where I had previously specified a clock, the clock is not being shown. [The main menu, and the workplace shifter, are shown - but do not respond.]
Looked in .xsession-errors. Mostly ALSA problems (I do not even use ALSA for anything!). Also some asserts that mean nothing to me, e.g.: (gnome-panel:4540): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (gnome-panel:4540): Wnck-CRITICAL **: wnck_screen_get_windows: assertion `WNCK_IS_SCREEN (screen)' failed (gnome-panel:4540): libgnomevfs-CRITICAL **: gnome_vfs_uri_new_private: assertion `text_uri != NULL' failed
I've tried deleting everything in the user's home directory that begins with '.g*' - that removes icons from the panel, but does not fix the problem. On at least one system, whether after a reboot I even get to see a panel seems to be random - sometimes when I log on I see the unresponsive panel, but at other times I get an error message something like "I've detected a panel already running - will exit now" -- result is a screen with _no_ panels shown.]
Would like to get the gnome panel functioning. Suggestions, please.
mikus
Sorry I do not have a solution for you, Mikus, but I would like to add I am seeing the exact same problem on one SuSE 10.0 box. -- --Moby