metacity doesn't launch

[Joachim Noreiko]

Binary package hint: metacity

When I start my computer up, there are no borders on the windows. I can't move any windows, I don't have workspaces. Firefox has covered up the applications menu, and my computer is effectively unusable.

[Christian Reis (kiko)]

Thanks for your report. I have a few questions about your report:

1. What release of Ubuntu are you using?
2. Have you enabled desktop effects (in other words, Beryl or Compiz)?
3. If you have a terminal available to type in, can you run the "metacity" command and tell me what happens?

[Joachim Noreiko (jnoreiko)]

1. Just upgraded edgy->feisty
2. No
3. Borders appear on all windows and everything seems to go back to normal. I get a few warning messages about my custom theme, like:
Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.

[Sebastien Bacher (seb128)]

Do you use session saving? Does moving .gnome2/session somewhere else fixes the bug? It might be a duplicate of bug #106350

[Joachim Noreiko (jnoreiko)]

I tried:
joachim@ubuntu:~/.gnome2$ mv session ~
and then logged out. On login, metacity still didn't launch.

[Christian Reis (kiko)]

Can you mv your entire ~/.gnome2 directory and retry? I wonder if there's a log we could use to check what's going on..

[Joachim Noreiko (jnoreiko)]

I did:
joachim@ubuntu:~$ mv .gnome2 .gnomemoved

Logged out, logged in: metacity launched as normal.
Tried logging out and in again once more just to make sure: still launches correctly.

[Sebastien Bacher (seb128)]

did you use the session saving option before? in which case that's likely a duplicate as mentionned before

[Joachim Noreiko (jnoreiko)]

Today's experiments:
1. I booted my PC today -- metacity didn't launch.
2. I tried disabling the Sessions saving options, and logging out, and nack in: metacity launches.
3. I installed the software update with the fix for Bug #106350, re-enabled session saving, logged out and back in: metacity didn't launch.
4. I rebooted, metacity launched.

I suppose 3 is due to bad session data being left over from before the upgrade?

[Sebastien Bacher (seb128)]

did you restart your session after the update, it's required to have the new version used

[Joachim Noreiko (jnoreiko)]

No, I didn't. I performed only the steps I listed.

I've since rebooted, and metacity has launched as normal: the update appears to have fixed the problem, hence this was a duplicate.
Thanks Sebastien and Christian for your help :)

[Sebastien Bacher (seb128)]

marking duplicate then