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
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
On Tuesday 19 September 2006 15:35, Mikus Grinbergs wrote:
Would like to get the gnome panel functioning. Suggestions, please.
Hi Mikus, I successfully upgraded my 10.0 system using SUSE's supplementary branch, but it was some time back and I've forgotten the details. However, I seem to recall a rather serious conflict with libwnck(spelling?) that would not resolve easily... that and one with evolution-data-server. It's a bit of a slog, but here's how I accomplished it: * add the supplementary GNOME branch to your YaST installation sources * launch the 'Software Management' module * enable the filter "Selections", top-left * turn off "Autocheck" for dependencies * highlight "GNOME system" in the left pane * for each blue (can be upgraded) item in the right pane: - click the checkbox once to enable 'update' - click the "Check Dependencies" button * when "All package dependencies are OK" displays, try the next item * when, instead, a conflict is generated, click "Cancel" and reset to "keep" The goal is to proceed through the entire list of "Gnome system" packages and click "Accept" to upgrade as many as possible without encountering/causing conflicts. Try this procedure and see if it doesn't clear your problem up. For reference, following is the result of an 'rpm -qa | grep gnome' from my 10.0 system. hth & regards, Carl carl@linux:~> rpm -qa | grep gnome gnome-panel-2.12.0-5 python-gnome-2.12.3-18 gnome-utils-2.12.2-35 python-gnome-extras-2.11.3-3 hal-gnome-0.5.4-6.4 gnome-printer-add-1.0.1-16 gnome-doc-utils-0.5.3-15 gnome-pilot-2.0.13-20 gnome-desktop-2.12.2-26 gnome-keyring-0.4.6-21 libgnomeui-2.12.0-30 libgnomecups-0.2.2-21 gnome-menus-2.12.0-32 libgail-gnome-1.1.2-16 gnome-mime-data-2.4.2-22 gnome-nettool-1.4.1-18 gnome-screensaver-2.14.0-25 gnome-netstatus-2.12.0-19 gnome-backgrounds-2.12.2-15 gnome-icon-theme-2.12.1-27 gnome-terminal-2.12.0-23 libgnomesu-1.0.0-33 gnome-session-2.12.0-121 gnome-filesystem-0.1-264 gnome2-user-docs-2.8.1-21 gnome-mag-0.12.2-18 gnome-vfs2-2.12.2-67 gnome-system-monitor-2.12.2-35 libgnomedb-1.3.91-23 gnome-themes-2.12.1-35 libgnomecanvas-2.12.0-19 libgnome-2.12.0.1-30 gnome-cups-manager-0.32cvs20060120-41 xmms-gnome2-0-526 gnome2-SuSE-10.1-31 gnome-volume-manager-1.5.15-28 gnome-games-2.12.2-3 gnome-libs-1.4.1.7-710 gnome-applets-2.12.0-3 libgnomeprint-2.12.1-23 OpenOffice_org-gnome-2.0.0-1.4 libgsf-gnome-1.13.99-15 gnome-keyring-manager-2.12.0-20 gnome-bluetooth-0.6.0-5 gnome-media-2.12.0-7 gnome-audio-2.0.0-134 gnome-speech-0.3.9-18 gnome-spell2-1.0.6-22 libgnomeprintui-2.12.1-20
On Tue, 19 Sep 2006 22:11:11 -0400 Carl Hartung
On Tuesday 19 September 2006 15:35, Mikus Grinbergs wrote:
Would like to get the gnome panel functioning. Suggestions, please.
Hi Mikus,
I successfully upgraded my 10.0 system using SUSE's supplementary branch, but it was some time back and I've forgotten the details. However, I seem to recall a rather serious conflict with libwnck(spelling?) that would not resolve easily... that and one with evolution-data-server.
It's a bit of a slog, but here's how I accomplished it:
* add the supplementary GNOME branch to your YaST installation sources * launch the 'Software Management' module * enable the filter "Selections", top-left * turn off "Autocheck" for dependencies * highlight "GNOME system" in the left pane * for each blue (can be upgraded) item in the right pane: - click the checkbox once to enable 'update' - click the "Check Dependencies" button * when "All package dependencies are OK" displays, try the next item * when, instead, a conflict is generated, click "Cancel" and reset to "keep"
The goal is to proceed through the entire list of "Gnome system" packages and click "Accept" to upgrade as many as possible without encountering/causing conflicts.
Try this procedure and see if it doesn't clear your problem up.
Haven't tried it - principally because adding YaST installation sources has always seemed too arcane a subject for me. Maybe if I get desperate enough ?!? [I instead use 'smart --gui' (and sometimes 'apt-get') to access 3rd party repositories.]
For reference, following is the result of an 'rpm -qa | grep gnome' from my 10.0 system.
Carl
carl@linux:~> rpm -qa | grep gnome
The 10.0 system that is accessible to me at home was almost identical to what you listed. The principal difference was that on my system, 'gnome-panel' and 'gnome-applets' were at the 2.12.2 level (gotten off the gnome repository) whereas yours were at the 2.12.0 level (gotten off the base repository). Just to be equal, I downgraded these two packages to also be at the 2.12.0 level. It made no difference - I still keep getting all the problem symptoms I described earlier. Not counting things I don't need such as 'gnome-pilot', the only remaining differences between my sytem and yours are the presence on my system of the following extra packages (which to me don't seem significant). Maybe I'll try deleting them, but don't have much hope: gnome-vfs-1.0.5-840 gnome-commander-1.1.7-2 gnome-print-0.37-23 gnome-panel-debuginfo-2.12.0-5 gnome-system-tools-1.4.1-20 gnome-printer-add-1.0.1-16 gnome-common-2.12.0-14 Thank you, Carl, for your help -- but at the moment I'm still stuck. Tomorrow I'll try fooling around with libwnck. mikus
On Wednesday 20 September 2006 02:09, Mikus Grinbergs wrote:
Haven't tried it - principally because adding YaST installation sources has always seemed too arcane a subject for me. Maybe if I get desperate enough ?!? [I instead use 'smart --gui' (and sometimes 'apt-get') to access 3rd party repositories.]
Hi Mikus, I understand this approach completely, but I've never had a successful GNOME mass update with SUSE... it's always ended up being a 'hunt and peck'. Have you created a test user to see if the pristine GNOME environment it produces also 'hiccups' the same way?
The 10.0 system that is accessible to me at home was almost identical to what you listed. The principal difference was that on my system, 'gnome-panel' and 'gnome-applets' were at the 2.12.2 level (gotten off the gnome repository) whereas yours were at the 2.12.0 level (gotten off the base repository).
This is one of the conflicts I'd forgotten about: I *can't* update gnome-applets because the ensuing rpm database conflict won't resolve. You haven't, by any chance, gotten into the habit of using '--force' with CLI rpm, have you?! I know some users do this to 'overcome' dependencies and conflicts, but <tsk tsk tsk>! if you have! BTW, You can use reset previously ignored conflicts and dependencies (then play . :-)
Thank you, Carl, for your help -- but at the moment I'm still stuck. Tomorrow I'll try fooling around with libwnck.
I never found a solution other than avoiding that particular conflict; ditto gnome-panel. Good luck! Carl
participants (3)
-
Carl Hartung
-
mikus@bga.com
-
Moby