You are not logged in.
I installed clfswm with packer, and put the line "exec clfswm" into .xinitrc. startx, and I get this http://sprunge.us/BUJg on TTY and this to /var/log/Xorg.0.log http://sprunge.us/CScI
Other WMs work (spectrwm is all I've tried so far)
I'm not sure what the issue is. I've just installed arch and still haven't installed most of my packages, so it wouldn't be unreasonable if I was missing something stupid, I've never installed X manually before.
Solved this by installing xdg-utils and using xinit instead of startx.
Last edited by thevdude (2012-07-21 23:24:15)
Offline
Interesting ... I love tinkering with new WMs.
I just tried it out and it worked perfectly here. Can you post your .xinitrc.
edit: what is the output of
echo $XDG_CACHE_HOMEI'm guessing you do not have this variable set, in which case the error you are seeing would make sense. If you look at the code of the clfswm script, it sets "dump_path" to $XDG_CACHE_HOME/clfswm/ without checking whether the XDG variable is set. If the variable is not set, "dump_path" is just /clfswm/. When the script later calls 'mkdir $dump_path` you get the permission error for trying to create a directory in the root directory rather than your user's home directory.
You can avoid this by ensuring XDG_CACHE_HOME is set to something reasonable either by installing the appropriate XDG package, or just set it yourself to /home/USERNAME/.config.
I'd also suggest reporting this as a bug to the maintainer. The script should definitely ensure that variable exists before it attempts to use it like that.
edit2: I suspect the xdg variable is set by something in extra/xdg-utils. Perhaps this package should be added as a dependency for clfswm.
Last edited by Trilby (2012-07-20 22:22:39)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Well, that fixed one issue and lead to another.
I'm getting "CLFSWM Error: Connection Failure to X11.0 server display 0: No protocol specified"
xdg-utils fixed it otherwise though.
Offline
OK, now can you post your .xinitrc? Also, have you tried starting with just `xinit`.
edit: also the tty output from X with the new error would be useful.
Last edited by Trilby (2012-07-21 03:27:53)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Moving to "AUR Issues, Discussion and PKGBUILD requests"
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
.xinitrc just has #!/bin/sh and exec clfswm.
startx doesn't work, xinit does.
Terminal output for startx (removed a large section of it repeating) is http://sprunge.us/XXMQ
Works fine with xinit, I wonder what the difference is ![]()
Offline
I always just use xinit and avoid startx, I don't see any purpose (for my use) to use startx. Startx is a script that does a variety of different stuff[1] then calls xinit itself.
if you really want to get to the bottom of why startx fails, check out the startx script. Particularly look for anything that may set the DISPLAY variable. Note though, that you'll have to dig through dozens of other files which may be sourced by the startx script ... some of them in turn source other files.
[1]: Some may find some of this 'stuff' useful, but if I need anything more than xinit, I'd prefer to do it myself and have control of it.
edit: I can verify that CLFSWM fails with the same error here when I try to start via startx, but xinit works fine.
Last edited by Trilby (2012-07-21 16:36:33)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
That's good enough for me. I'll end up looking through startx some time to see what happens, but xinit seems like a better choice anyway.
Offline
Cool. If it's working you can mark this thread as solved (by clicking edit on your initial post to change the title).
Also, if you're up for it, a wiki article on CLFSWM would be handy ... assuming you've used it before and/or are learning about it. It strikes me as interesting enough to merit some playing around in, but a tutorial of it's major features or configurations would be nice, as it does seem to use a very different desktop "metaphor" than either floating or tiling WMs.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline