GNOME Bugzilla – Bug 92574
funny gnome-settings-daemon error on sawfish session startup
Last modified: 2004-12-22 21:47:04 UTC
Package: control-center Severity: normal Version: 2.0.1.1 Synopsis: funny gnome-settings-daemon error on session startup Bugzilla-Product: control-center Bugzilla-Component: settings-daemon Description of Problem: As of recently, gnome-settings-daemon always encounters a type mismatch error on startup: 'got list of list, expected list of list'. While this is rather funny, it's also rather annoying. :/ It seems to work perfectly afterwards though. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-09-05 09:32 ------- Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Just point out that I'm seeing this problem too. The dialog seems to appear when it launches (or just before) Metacity.
It disappears after moving away ~/.gconf/desktop/gnome/applications/window_manager
Yup same thing happened to me after upgrading. using debian. I wil try the above fix and see it helps.
*** Bug 97394 has been marked as a duplicate of this bug. ***
*** Bug 96210 has been marked as a duplicate of this bug. ***
I do not believe this is a 2.0 issue, so removing GNOMEVER2.0 keyword.
*** Bug 97880 has been marked as a duplicate of this bug. ***
FWIW this is probably a 2.2.0 blocker
Very borderline blocker, but yeah, probably a blocker if it is actually gnome-cc's fault and not an installation or sawfish problem.
Can anyone test this and see if it's still a problem, please?
Hmm. Recently on debian-gtk-gnome, someone said how to reproduce this... it could be reproduced changing some setting in the WM, IIRC, maybe the viewport/workspace/whatever they are called name. I'm quite sure I never did that though, so there must be other ways. Can't test if it happens myself, I'm 1) not using GD2.1 and 2) not sure of how to reproduce it right now.
I haven't seen the problem in a long while. Michael, have you? We both use Debian.
I assume you're asking me, as I don't see a Michael here. ;) I don't know how to reproduce it either...
This bug was mentioned quite a lot in user mailing lists and forums. I haven't seen it mentioned for a long time, and 2 people here can't reproduce it. So I'm going to close this bug, but reopen if we get another report.