Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[gentoo-user] Re: gconfd-2 woes

56 views
Skip to first unread message

Stefan G. Weichinger

unread,
Mar 22, 2012, 3:10:01 PM3/22/12
to
Am 2012-03-22 19:52, schrieb Stefan G. Weichinger:
>
> greets,
>
> today I wanted to be clever and ran "emerge -e gnome" to rebuild all my
> gnome-3 desktop.
>
> Unfortunately things didn't get better from this.
>
> I can hardly logon, gconfd-2 produces high load and
> /var/lib/gdm/.gconfd/saved_state grows quickly to around 4 GB until it
> fills the disk :-(
>
> I removed that file while gdm was not running, no matter, it got created
> again ...

addon: it seems full of pulseaudio-related lines ... maybe I should
rebuild that one now as well

Stefan G. Weichinger

unread,
Mar 22, 2012, 3:10:02 PM3/22/12
to

greets,

today I wanted to be clever and ran "emerge -e gnome" to rebuild all my
gnome-3 desktop.

Unfortunately things didn't get better from this.

I can hardly logon, gconfd-2 produces high load and
/var/lib/gdm/.gconfd/saved_state grows quickly to around 4 GB until it
fills the disk :-(

I removed that file while gdm was not running, no matter, it got created
again ...

So right now I have no desktop on my desktop, writing this from the
thinkpad.

Could someone point me at how to start debugging this?

I already rebuilt gdm, gconf, gnome-session ... revdep-rebuild shows
nothing, dispatch-conf either

Thanks, Stefan

walt

unread,
Mar 22, 2012, 4:00:01 PM3/22/12
to
Or delete it ;) If that doesn't work I would start by creating a new test
user account and run gnome-3 from there. The problem may be caused by one
of the zillion gnome config files in your home directory.

Canek Peláez Valdés

unread,
Mar 22, 2012, 4:30:02 PM3/22/12
to

You

You can remove /var/lib/gdm, and reemerge gdm. It usually works for me.

Regards.

Stefan G. Weichinger

unread,
Mar 22, 2012, 6:40:03 PM3/22/12
to
The problem starts even before I log in!

S

Stefan G. Weichinger

unread,
Mar 22, 2012, 6:50:01 PM3/22/12
to
Am 2012-03-22 21:14, schrieb Canek Peláez Valdés:
> You
> El 22/03/2012 13:04, "Stefan G. Weichinger" <li...@xunil.at
> <mailto:li...@xunil.at>> escribió:
that helped a bit .... the saved_state file now peaks at around 500 MB
... but the shell(?) crashes again.

I see lots of:

gconfd-2[18280] general protection ip:7f24944dfa5f sp:7fffc4f6bfe8
error:0 in libc-2.14.1.so[7f24943c7000+181000]


in "dmesg".

As mentioned, gconf has been rebuilt already.

I also didn't change anything in terms of (un)masking stuff when I
re-emerged gnome today.

[I] gnome-base/gconf
Available versions: (2) 2.32.3 2.32.4 (~)3.2.3
{{debug doc +introspection ldap +orbit policykit}}
Installed versions: 3.2.3(2)(18:50:53 22.03.2012)(introspection
orbit policykit -debug -doc -ldap)

[I] sys-libs/glibc
Available versions: (2.2) (~)2.9_p20081201-r3!s 2.10.1-r1!s
2.11.3!s (~)2.12.1-r3!s 2.12.2!s (~)2.13-r2!s 2.13-r4!s (~)2.14!s
(~)2.14.1!s (~)2.14.1-r1!s (~)2.14.1-r2!s **2.15!s **9999!s
{{crosscompile_opts_headers-only debug gd glibc-omitfp hardened
multilib profile selinux vanilla}}
Installed versions: 2.14.1-r2(2.2)!s(00:48:53 20.01.2012)(multilib
-crosscompile_opts_headers-only -debug -gd -glibc-omitfp -hardened
-profile -selinux -vanilla)

restarted xdm, saved_state grows again, and this is *before* I even get
the login.

S

Stefan G. Weichinger

unread,
Mar 22, 2012, 7:40:02 PM3/22/12
to
sure, I rebuilt glibc now and gconf after that.
Still same symptoms :-(

S

Stefan G. Weichinger

unread,
Mar 23, 2012, 3:40:01 AM3/23/12
to
Am 23.03.2012 00:32, schrieb Stefan G. Weichinger:

> sure, I rebuilt glibc now and gconf after that.
> Still same symptoms :-(

I solved it halfways by:

quickpkg gconf on my thinkpad
mv it over and emerge it on the problematic machine

re-emerge gvfs
removing saved_state files (in /var/lib/gdm/.gconfd and ~/.gconfd)

right now the gnome-session is UP

If I re-emerge gconf here I get the same crashes and protection errors.

So I will keep it this way for now.

I wanted to get rid of any hidden problems with my "emerge -e gnome"
yesterday. Didn't work out as expected.

greets, Stefan
0 new messages