[probably SOLVED] xmonad + gnome again

Question

Hi folks!
After running 'plain' xmonad-darcs for a time i'd like to run gnome together with xmonad, so installed gnome today (haven't used it for years). gnome is up and running, but i can't get to get it run with xmonad as it's wm~
Of course i've tried to follow xmonad's wiki... I used other people's xmonad.hs, that basic one or that other one; additionally, xmonad-contrib-darcs v20081207-1 is installed. For completeness, I actually just use
-- xmonad.hs
import XMonad
import XMonad.Config.Gnome
main = xmonad gnomeConfig
It seems, that somehow xmonad can't be imported: a new created ~/.gnomerc makes no change, same with a copied  "export WINDOW_MANAGER=xmonad"  in ~/.profile (which is sourced by .xinitrc) or even in ~/.xinitrc itself. I added xmonad to the list of starting programs in gnome's session manager as well, I disabled nautilus and changed the position of the panel... Trying to start gnome with this:
export WINDOW_MANAGER=xmonad
exec gnome-session --purge-delay=3000
it says that --purge-delay is an invalid option (so i guess that is meant to work with an older version of gnome).
Then it comes up to gnome-session. But in my gnome there is no possibility to "select Metacity and change style to Trash"!? (Within the "sessions" I only can add starting programs or tell which applications to remember.)
Nevertheless, I can start an xterm and run "killall metacity; xmonad &"; then metacity disappears, windows are indeed tiling, but in the xterm there's the following output:
$ unknown ClientMessageEvent 269
unknown ClientMessageEvent 269
unknown ClientMessageEvent 269
unknown ClientMessageEvent 269
unknown ClientMessageEvent 269
and the system becomes almost unusable. After killing the xterm metactiy reappears.
I wonder how Phrodo_00 solved his problem, seemed to be trivial...
Any ideas?
Last edited by nexus7 (2009-01-11 14:07:52)

Answer 1

Ugh!
Because starting x takes always 5-10 minutes I liked to speed it up. I thought it still could be gnome fighting against xmonad, since here xmonad is added as starting program while at the same time you have the "/usr/share/applications/xmonad.desktop" (see above). So I liked to  see what happens after deselecting xmoand as starting program in the sessions manager... But from now on gnome wouldn't  start at all anymore! Neither
gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager metacity
nor
rm -rf ~/.gnome* ~/.gconf*
helped (I don't have a ~/.gnome2/session)! X just hangs after showing its cursor, and there are heavy cooling but lesser disk activities -- so how to reactivate plain gnome??
But also suddenly another problem seem to arise (but for heavens sake, why~ there weren't any before...):
In the first time I crashed X that error was shown in the console:
(EE) intel(0): underrun on pipe B!
-- But how comes?, I disabled these in /etc/xorg.conf:
Section "ServerFlags"
Option "AutoAddDevices" "False"
Option "AutoEnableDevices" "False"
EndSection
Now there's another one:
error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid argument (22)
Disgusting~
Nevertheless running plain xmonad works... ((edit: after exchanging the xmonad.hs of course))
Last edited by nexus7 (2009-01-11 12:03:52)