Comment 14 for bug 105390

shirishag75 wrote:
> ok would try that, just to inform the number of things which were tried so everybody knows.
> actually the command which u gave in the morning DISPLAY=:0 metacity --replace && use to give a warning
>
> shirish @ubuntu $ Window Manager manager warning "found in
> configuration database is not a valid value for keybinding
> "toggle_shaded"

That doesn't look like a serious problem.

> which escalated to the afternoon to :-
> shirish @ubuntu $ Window Manager manager warning "found in configuration database is not a valid value for keybinding "toggle_shaded"
> Window Manager error= " Unable to open X display 0"

That looks like you forgot the colon again :)

> shirish @ubuntu $ Window Manager manager warning "found in configuration
> database is not a valid value for keybinding "toggle_shaded"
>
> xlib: connection to "0.0" refused by server
> xlib: No protocol specified

This probably means :0 isn't owned by you (perhaps the test user was
running that session?); that's why I talked about checking the value in
~/.xsession-errors.

> Further things tried by seb128 :-
>
> gconftool --2 --get /desktop/gnome/application window_manager/default ?
>
> /usr/bin/metacity
>
> failed to get a value for '?' Bad key or directory name '?" Must begin with a slash (/)

That's because he hadn't actually meant the "?" to be typed. Otherwise,
it worked fine. (And, he just wanted to get the /usr/bin/metacity value:
he wasn't expecting it to fix anything.)

> was asked if there was any .dmrc directory in /home/username which
> was replied in negative
>
> was asked to move the file ~/.gnome2/session which had no effect
>
> then tried sudo apt-get install --reinstall metacity_common which
> again did not result into anything better
>
> The only solution which works in the meanwhile is typing
> 'metacity' without the quotes in terminal brings all window decorations
> etc.

What this essentially means is that running metacity by hand fixes
things, but for some reason metacity is either not running by default in
your gnome session, or is crashing for some strange reason. moving
~/.gnome2/session seems like it should have fixed it; but ~/.gnome2
definitely ought to: it's just a bit draconian (though not as much so as
blowing away the user's home directory), since any customizations to
gnome apps that you've done will have to be redone.

Thanks for the run-down, shirish!