Re: Metacity crashing after today's upgrade?

[Robin Putters <rputters@hotpop.com>]

On Tue, 2002-12-17 at 22:17, Robin Putters wrote:
> > I too describe the same problem some of you are reporting. I first
> > triggered it when I tried to change the default workspace names to
> > something else -- I've seen it happen through using gconf-editor and
> > workspace switcher.
> > 
> > It seems to corrupt gconf in a bad way and I could only get things
> > working again by removing the .gnome2 and .gconf/.gconfd directories

This is the last part of the trace:

read(6, "\34>\257\0009\0\0\0\25\1\0\0\234\261\367\16\0\370\377\277"...,
32) = 32
read(6, "\1 \260\0\3\0\0\0\6\0\0\0\0\0\0\0\3\0\0\0\0\0\0\0\0\0\0"...,
32) = 32
read(6, "\0\0\0\0\2\0\0\0\0\0\0\0", 12) = 12
write(6, "\24\0\6\0009\0\0\0\370\0\0\0\354\0\0\0\0\0\0\0\377\377"...,
24) = 24
read(6, "\1\10\261\0\f\0\0\0\354\0\0\0\0\0\0\0000\0\0\0\0\0\0\0"..., 32)
= 32
readv(6, [{"Workspace 1\0Workspace 2\0Workspac"..., 48}, {"", 0}], 2) =
48
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

Deleting my .gconf / .gnome directories doesn't help at all. I even
started metacity by creating a new user to make sure it wasn't some
corrupt user setting.

Very weird...

-- 
Robin Putters <rputters@hotpop.com>