-   Linux - Software (
-   -   Xmonad launch error (

ADX 07-28-2011 11:07 AM

Xmonad launch error
I originally attempted to compile and install xmonad package by package, and the end result was this:


$ xmonad
/home/adx/.xmonad/xmonad-x86_64-linux: executeFile: does not exist (No such file or directory)
X Error of failed request:  BadAccess (attempt to access private resource denied)
  Major opcode of failed request:  2 (X_ChangeWindowAttributes)
  Serial number of failed request:  7
  Current serial number in output stream:  8

I figured I left out a flag on the make file or something, so I tried the slackbuild packages next; however, the same error was present at launch.

Anyone have any ideas?

TobiSGD 07-28-2011 01:26 PM

Normally Xmonad isn't installed into ~/.xmonad/, that is where the configuration file is expected. This file has to be present to launch Xmonad, and it won't generate a standard file. So I would assume that you have no configuration file, have a look at that.

Predatorian 09-07-2014 09:51 PM

Bumping this since OP didn't respond. I'm interested in this answer as well, but not sure what to find.

Predatorian 09-07-2014 10:27 PM

Ok, so, I got xmonad to do something for me, but now I need to figure out what I'm going to do about my terminal.

I looked around and found this configuration guide. Quite simple.

Arch Linux - Configuring XMonad

A lot of, and most of these tutorials I found are for Arch Linux, but once you have the XMonad program compiled for your system, you're over the OS Dependent hump. Now its just configuration. So, following the Arch Linux tutorials will also work for CentOS, or whatever other OS you're running.

This is also a more fully configured xmonad.hs file. xmonad.hs file

This is also a good place to look as well.'s_Configuration

Now, after getting all that configured and recompiled


xmonad --recompile
I ran into an error that was very frusterating and annoying because of the lack of output and no real error log.

When running the command


to start xmonad, I would receive this error:


xmonad-i386-linux: user error (openDisplay)
and according to this: Xmonad fails at starting up, what I was needing to do was make X startup xmonad, or start it using


xinit xmonad
Once that was done, I could start it up, and run it. Now I'm just figuring out my configuration.

Predatorian 09-07-2014 10:37 PM

Well, with my default configuration, I just get an XTerm window, even with the urxvt option, and no prompt. Then it just sits there and looks at me like I'm stupid. Then the configs from the website that are predefined, throw errors that some functions are not available.

Mind you, I'm doing this on CentOS.

All times are GMT -5. The time now is 12:38 PM.