| View previous topic :: View next topic |
| Author |
Message |
kb1lqc
n00b
Joined: 27 Sep 2010
Posts: 9
|
 Posted: Mon Sep 27, 2010 6:00 pm Post subject: Gnome Window Manager Problem [SOLVED] |
 |
|
I accidentally removed the window manager in GNOME 2.30.2 with the "main menu" editor. This apparently removed my WM and now the windows all start in the upper left corner of the screen and cannot be moved or anything. I have switched to KDE in the meantime but would like to fix the problem. What should I do? I am not new to Linux but am relatively new to Gentoo. If more information is needed about my system just let me know.
Last edited by kb1lqc on Wed Oct 06, 2010 3:56 pm; edited 1 time in total |
|
| Back to top |
|
 |
Manko10
Tux's lil' helper
Joined: 20 Aug 2010
Posts: 105
|
| Posted: Mon Sep 27, 2010 6:15 pm Post subject: |
|
|
Have you reemerged metacity?
If that doesn't help run | Code: | metacity --replace &
disown |
on your terminal under Gnome.
_________________
Refining Linux Advent calendar series 2010: “24 Short Linux Hints” |
|
| Back to top |
|
|
kb1lqc
n00b
Joined: 27 Sep 2010
Posts: 9
|
| Posted: Mon Sep 27, 2010 10:28 pm Post subject: Gnome Window Manager Problem - response |
|
|
OK I reinstalled metacity and tried to run it with your commands in GNOME 2.30.2 and I obtain the following output (as root):
| Code: | bryce-dell bryce # metacity --replace
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: "(null)" found in configuration database is not
a valid value for mouse button modifier
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Could not parse font description "(null)" from
GConf key /apps/metacity/general/titlebar_font
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: 0 stored in GConf key
/apps/metacity/general/num_workspaces is out of range 1 to 36
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
Window manager warning: 0 stored in GConf key
/desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128
GConf Error: Failed to contact configuration server; some possible
causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; some possible
causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; some possible
causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; some possible
causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
**
metacity:ERROR:core/prefs.c:2482:meta_prefs_get_workspace_name:
assertion failed: (workspace_names[i] != NULL) |
Thank you for your help and hopefully this extra bit of information is useful.
Bryce |
|
| Back to top |
|
|
Abraxas
l33t
Joined: 25 May 2003
Posts: 814
|
| Posted: Tue Sep 28, 2010 12:02 pm Post subject: |
|
|
You have to run Metacity as your normal user not root.
_________________
Time makes more converts than reason. - Thomas Paine
Travel is fatal to prejudice, bigotry, and narrow-mindedness, and many of our people need it sorely on these accounts. - Mark Twain |
|
| Back to top |
|
|
kb1lqc
n00b
Joined: 27 Sep 2010
Posts: 9
|
| Posted: Tue Sep 28, 2010 12:08 pm Post subject: |
|
|
| Abraxas wrote: | | You have to run Metacity as your normal user not root. |
That does work. I now have a window manager in GNOME but only for this session. I tried logging out and back in which resulted in me having to start metacity again. Thanks for the help!
Bryce |
|
| Back to top |
|
|
Abraxas
l33t
Joined: 25 May 2003
Posts: 814
|
| Posted: Thu Sep 30, 2010 10:57 pm Post subject: |
|
|
Makre sure the /desktop/gnome/session/required_components gconf key includes metacity.
_________________
Time makes more converts than reason. - Thomas Paine
Travel is fatal to prejudice, bigotry, and narrow-mindedness, and many of our people need it sorely on these accounts. - Mark Twain |
|
| Back to top |
|
|
kb1lqc
n00b
Joined: 27 Sep 2010
Posts: 9
|
| Posted: Tue Oct 05, 2010 7:31 pm Post subject: |
|
|
| Abraxas wrote: | | Makre sure the /desktop/gnome/session/required_components gconf key includes metacity. |
Where is this located? Might a be a dumb question but... |
|
| Back to top |
|
|
corphi
n00b
Joined: 19 May 2008
Posts: 20
|
| Posted: Wed Oct 06, 2010 12:47 pm Post subject: |
|
|
| GConf, the Gnome Configuration database. You can use gconf-editor to yiew and edit its stored settings. |
|
| Back to top |
|
|
kb1lqc
n00b
Joined: 27 Sep 2010
Posts: 9
|
| Posted: Wed Oct 06, 2010 3:56 pm Post subject: Solved! |
|
|
| Abraxas wrote: | | Makre sure the /desktop/gnome/session/required_components gconf key includes metacity. |
OK with the clarification from corphi and help from abraxas I got it working! The setting was set to gnome-wm which I changed to metacity. This got everything working again!
I did learn that you must run "gconf-editor" as non-root to see the configuration settings. Probably a stupid mistake running it as root since when that happened all I saw was "/" and couldn't see any settings. Live and learn I guess. I appreciate the help everyone!
Bryce Salmi
KB1LQC |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
