I posted this on gnomesupport.org, but got no help. So perhaps someone from here knows an answer.
Since some days my system is extremely slow on starting. From pressing the power button to a useable gnome desktop it takes half an hour (I observed the watch). I can start a terminal session (which is slower then usually too). top reveals this:
The rest of the list are processes which use no CPU or memory percentage. gconfd-2 uses up to 99% of the CPU and it seems to keep the HD busy too.
When I login to my gnome session this behavior goes on for another 15 minutes (estimated) before the system gets reactive again. When I logout from gnome without switching off the PC gconfd-2 gets busy again.
I remember having installed some gnome update from gnome factory (I don’t know how the factory repository was activated), but I switched all gnome packets which were from factory back to normal stable versions.
At the same time I installed a net drive from which I mount two shares (I can’t imagine that this is the reason for a hyperactive gconfd-2, but who knows…)
I reinstalled some system software and renamed some configuration files - all without success.
Any ideas what I could try?
openSuSE 11.2
GNOME 2.28.2
gconf 2.28.0-2.5
Thanks
Stephan
No, this didn’t change anything. The problem starts, before I log in. Should I delete my existing user data in case they are corrupted? If so - how could I back up my settings in case this doesn’t help?
joesse01 wrote:
> No, this didn’t change anything. The problem starts, before I log in.
> Should I delete my existing user data in case they are corrupted? If so
> - how could I back up my settings in case this doesn’t help?
since the problem begins before you log it is is NOT your user data,
so there is no need to delete it…(you ask how to back up your
settings, does that mean you do not have a backup from before the SLOW
began?)
what happens if you put in the 64 bit gnome live CD…does it boot
right up and run right?
what operating system and version are you using? is it fully updated?
how long did this system run well before these problems began?
and, in your first post the top output shows 1 zombie…what is that?
do you have a zombie showing everytime you boot up…
wait a second: in your first post you say you boot up to a desktop and
open a terminal…and, then you type what? top, do you type anything
else before you type ‘top’…i ask because it looks like you logged
into Gnome as root…is that right?
have you looked in /var/log/messages to see if there are any errors
you can trace to their source, and solve?
and, can you do the following in a terminal and copy/paste it back to
here:
zypper lr -d
and, last: have you googled to see if you are the only person with
such a problem?
I thought that perhaps the login process tries to gather information about the profiles before displaying the user selection window. But all the better…
And unfortunately no. I was about to install a net drive with samba shares when this started, and I use this mainly for backup purposes - too late :-/
I tried to download a live CD image at gnome.org. Either I am too stupid to find it or they don’t offer one right now… Somebody point me in the right direction?
I started with openSUSE 11.0 and it has been working well just until now. Except when I was messing with the display driver. (I am using radeon now and I am quite sure there are no ATI remainders in my system.
I don’t know what it was. I booted right now and watched top, but the zombie didn’t show up.
Once I logged into Gnome as root and got a serious warning. I have not done that ever since. What I do is: while the graphical login screen is loading I switch to the console by Ctrl-Alt-F1 and log in as root. I could also login as normal user, but in this situation I do mostly things that require super user powers, so … no, I didn’t type anything before top.
There are some errors like (I try to translate german messages)
May 7 19:01:06 zeus gdm-simple-greeter[4356]: WARNING: could not get gconf key '/apps/gdm/simple-greeter/recent-languages': Failure contacting the configuration server; possible reasons are , that TCP/IP is not activated for ORBit or that old NFS locks are set due to a system failure. Further Information is available at http://projects.gnome.org/gconf/ (Details – 1: No message could be sent to the GConf-daemon: 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.)
They mostly relate to /apps/gdm/simple-greeter, the first one is about /desktop/gnome/session/idle_delay. I - knowing nothing about this - imagine that the reply timeout expired because the system is already slow at that moment. But you might disagree.
Then there is
May 7 19:01:33 zeus gdm-simple-greeter[4356]: GLib-GObject-CRITICAL: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
May 7 19:01:33 zeus gdm-simple-greeter[4356]: GLib-GObject-CRITICAL: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
May 7 19:04:39 zeus gdm-simple-greeter[4356]: WARNING: Unable to parse history: (null) 1#012
May 7 19:09:22 zeus gdm-simple-greeter[4356]: CRITICAL: gdm_option_widget_set_default_item: assertion `item == NULL || gdm_option_widget_lookup_item (widget, item, NULL, NULL, NULL)' failed
Whatever that means.
# | Alias | Name | Aktiviert | Aktualisieren | Priorität | Typ | URI | Dienst
---+--------------------------------------------------------------+--------------------------------------------------------------+-----------+---------------+-----------+--------+----------------------------------------------------------------------------------+-------
1 | ATI | ATI | Nein | Nein | 99 | rpm-md | http://www2.ati.com/suse/11.2/ |
2 | ATI Repository | ATI Repository | Nein | Nein | 99 | rpm-md | http://www2.ati.com/suse/11.2 |
3 | Banshee_1 | Banshee | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/Banshee/openSUSE_11.2/ |
4 | GNOME:Backports:2.30 | GNOME:Backports:2.30 | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/GNOME:/Backports:/2.30/openSUSE_11.2/ |
5 | GNOME:Factory | GNOME:Factory | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/GNOME:/Factory/openSUSE_11.2/ |
6 | Main Update Repository | Main Update Repository | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/11.2/ |
7 | Packman | Packman | Ja | Ja | 99 | rpm-md | ftp://ftp.uni-erlangen.de/pub/mirrors/packman/suse/11.2/ |
8 | Packman Repository | Packman Repository | Nein | Nein | 99 | rpm-md | http://packman.mirrors.skynet.be/pub/packman/suse/11.2 |
9 | home:anyremote | home:anyremote | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/home:/anyremote/openSUSE_11.1/ |
10 | home:malcolmlewis:Gtk | home:malcolmlewis:Gtk | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/home:/malcolmlewis:/Gtk/openSUSE_11.2/ |
11 | http://download.opensuse.org/distribution/11.2/repo/oss/suse | http://download.opensuse.org/distribution/11.2/repo/oss/suse | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/distribution/11.2/repo/oss/suse |
12 | openSUSE 11.2-0 | openSUSE 11.2-0 | Nein | Nein | 99 | yast2 | cd:/// |
13 | openSUSE_Factory | openSUSE Factory | Ja | Ja | 98 | rpm-md | http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/ |
I did that and tried all sorts of hints or solutions; I posted on several forums and in d.c.o.u.apps.gnome. The only advice was to empty /tmp which didn’t help.
Boot to a terminal (press 4 then the boot option) log in as yourself. then run top. Are things slow? Is there a process eating CPU?
DeverD was suggesting you download the CD Gnome install version of Suse. Not get something from gnome.org
We need to determine if the problem is prior to or after the GUI is loaded. If it is the GUI something could be messed up in the gnome user config files.
If prior we need to see if there is a zombie process or some other problem
you need to go into YaST and disable repos numbered …
WAIT, that is such a mess i have no idea how you got that way or how
you can even boot up…
why are you accepting factory (BETA!! not ready for prime time)
packages? are you a sofware engineer? a software tester?
in this posting http://tinyurl.com/33xh7ld read very carefully the
paragraph beginning with “IMPORTANT: Note repositories are in essence
file servers on the internet”
> DenverD;2161717 Wrote:
>> and, last: have you googled to see if you are the only person with
>> such a problem?I did that and tried all sorts of hints or solutions; I posted on
> several forums and in d.c.o.u.apps.gnome. The only advice was to empty
> /tmp which didn’t help.
my question was not: Did you ask on any other forums? it was “have you
googled to see if you are the only person with such a problem?”
joesse01 wrote:
> Ah, ok… I booted the Life CD. It runs as fast as you would explect
> from a CD system. … Hope that helps.
it sure does, because it tells us that your hardware is probably
healthy…and it tells us your installed linux is SICK (when
compared to the one on the Live CD which you can’t setup wrongly
because it boots from read only media)…
having just looked at all the conflicting repos you have enabled i
have to say i’m not at all surprised your install is sick…
i guess if you set your repos to the magic four (oss, non-oss,
update and packman) recommended by the sage geek named oldcpu and then
in a root terminal do
zypper ref
zypper dup
you might have a healthy machine again—however, since i do not
know why you have been installing from factory i have no idea which
(if any) really important bits you may have installed…so, my
prescription might do more harm than good…be SURE to read my
caveat (link in sig) because your machine and its usefulness to you
is in your hands…
Thanks for your advice. Believe it or not - I wasn’t happy with these factory repositories. I once installed a factory version of ConsoleKit because it helped to fix a problem I was having. Then dependencies had to be resolved… and so on. My bad, sure enough.
Deleting the unnecessary repositories and downgrading some packages did neither harm nor fix the system. So I guess I’ll have to do a reinstallation. Last question: When I reinstall openSuSE - will it see the already installed user profiles and propose to use them?
joesse01 wrote:
> Last question: When I reinstall openSuSE - will it see
> the already installed user profiles and propose to use them?
yes…but you say profile_S_, does that mean more than one user?
well, it will “see” your /home and ask if you wanna use it, if you say
yest then it will ask if you want to use it (one of them as
yours)…you decide…
and IF the borked part of your system is in your /home then you will
still have the problems…
HEY, before you do anything else go ahead and add a new user, then log
out and into that new user and see if all is well…if so you know the
hidden files in your non-working user is hash and those in your new
working user are ok…
The issue reported by joesse01 is exactly equal to mine :.
In my case the problem raised up after I made a dist-upgrade enabling Gnome:STABLE:2.28 and then reverting to official repos.
Something get broken inside the files and I notice the same high resource consumption by gconfd-2.
The only workaround I found useful has been by changing the “gdm” statement into /etc/sysconfig/displaymanager to “kdm”.
Doing this I am able to login through KDE greeter into my GNOME desktop without any problems.
Soles boring things are that:
I receive a request from Seahorse (the wallet manager) to input my password in order to allow networkmanager to proceed with the network connection
when I want to logout I went switched back into KDE greeter since resulting impossible to logout/shutdown from inside GNOME.
I attempted a lot of ways to recover my gdm without success so I think I will wait until 11.3 final be ready, then I will proceed with a system upgrade.
EDIT:----- ups sorry, I didn’t read the second page of the thread. But anyway, maybe that helps … -----
Your repository list looks really weird, you should try to clean that and than clean up your system. Looks like you are using packages from factory repository which is unstable - so now your installation is - guess what - unstable.
