bvc Posted January 10, 2003 Report Share Posted January 10, 2003 email reply Hi, Glad most of you are getting further at least. When you run "make install" it should copy fluxspace.py from src/ to someplace like /usr/local/lib/python2.2/site-packages. Check if it's there. If it looks like fluxspace.py was copied correctly, try running "python" stand-alone from the command line. Once you see the ">>> " prompt, type "import fluxspace" and press Return. You will probably see the same error as above. It would be interesting if you don't. As a diagnostic run the following commands. Just enter the ones preceded by ">>> ". I'm showing my output for reference. Python 2.2.2 (#1, Dec 26 2002, 22:54:33) [GCC 3.2.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> print sys.path ['', '/usr/local/lib/python2.2/site-packages', '/opt/debian/bin', '/usr/local/bin', '/home/scooper/bin', '/usr/lib/python2.2', '/usr/lib/python2.2/plat-linux2', '/usr/lib/python2.2/lib-tk', '/usr/lib/python2.2/lib-dynload', '/usr/lib/python2.2/site-packages', '/usr/lib/python2.2/site-packages/gtk-2.0'] >>> Notice that '/usr/local/lib/python2.2/site-packages' is in my path. Check that yours has what is needed to find fluxspace.py. If it doesn't you may have to create or edit a sitecustomize.py file to add your python library install path, e.g. /usr/local/lib/python2.2/site-packages to the python path for loading modules. I've attached a copy of my sitecustomize.py. If you're installing under /usr/local you should be able to just put this in /usr/lib/python<version>, unless there's already one there. Hope this helps. Please let me know how it goes. Steve Havent tried it yet....late for work :wink: Quote Link to comment Share on other sites More sharing options...
ezroller Posted January 10, 2003 Report Share Posted January 10, 2003 hehe, and I'll try as soon as I get to work. I'd hate to break my box at home. rather do that to one of my work PC's!!!!! 8) Quote Link to comment Share on other sites More sharing options...
tyme Posted January 10, 2003 Author Report Share Posted January 10, 2003 i'm going to guess that the problem is that by default this fluxspace.py file is going into /usr/local/lib instead of /usr/lib/ i forget, does fluxspace have a ./configure? if so..try the following instead of just ./configure: ./configure --prefix=/usr try that, and do make and make install. might make a difference? i would try it myself, but i'm at work, and my RH 8.0 box can't even get as far as Mandrake in the compile. it spits out some other error, i don't feel like trying to fix it. Quote Link to comment Share on other sites More sharing options...
ezroller Posted January 10, 2003 Report Share Posted January 10, 2003 is it safe to do tyme's suggestion if I have already installed this into /usr/local/lib? Quote Link to comment Share on other sites More sharing options...
tyme Posted January 10, 2003 Author Report Share Posted January 10, 2003 is it safe to do tyme's suggestion if I have already installed this into /usr/local/lib? the best thing would be to remove (manually) the original files, before you redo it. but even then, what i suggested still might not work-it's just a guess. from my experience, as long as nothing is depending on something you installed, it's not a big deal to delete it. and since fluxspace isn't depended on by any other programs, it should be a simple thing to remove it. Quote Link to comment Share on other sites More sharing options...
bvc Posted January 10, 2003 Report Share Posted January 10, 2003 Why not just make uninstall make clean? ./configure --prefix=/usr make, ect.... or just delete everything and start over :wink: Quote Link to comment Share on other sites More sharing options...
ezroller Posted January 10, 2003 Report Share Posted January 10, 2003 see despite my infinate linux wisdom, :roll: :roll: :roll: this is still something I'm not clear on. would i literally make uninstall fluxspace and what directory would I do this in? :?: Quote Link to comment Share on other sites More sharing options...
tyme Posted January 10, 2003 Author Report Share Posted January 10, 2003 see despite my infinate linux wisdom, :roll: :roll: :roll: this is still something I'm not clear on. would i literally make uninstall fluxspace and what directory would I do this in? :?: actually..if you left the directory which you built fluxspace in, you would just do make uninstall in that directory. atleast..that's how I undersatnd it... if you deleted that directory (like I always do) then you just have to use the "find and delete" method :) but...i'm not sure...? Quote Link to comment Share on other sites More sharing options...
ezroller Posted January 10, 2003 Report Share Posted January 10, 2003 Thats what I figured.....oh well. the MDK box I have at work is where I test things so I don't break the one at home, so I guess its time to learn. Quote Link to comment Share on other sites More sharing options...
Guest joehill Posted January 10, 2003 Report Share Posted January 10, 2003 I think doing ./configure --prefix=/usr worked. when I run fluxspace now, I get: joehill@node1:~/downloads/fluxspace/fluxspace-0.0.3>$fluxspace fluxspace: No configuration loaded <abort> so I guess if I had enough brains to figure out how to edit the configuration file... good thinkin' Tyme. course now I'm getting into this Waimea thing :roll: Quote Link to comment Share on other sites More sharing options...
ezroller Posted January 10, 2003 Report Share Posted January 10, 2003 BAM...in the readme it talks about moving a file called fluxspace.xml over to the ~/.fluxbox directory. Quote Link to comment Share on other sites More sharing options...
ezroller Posted January 10, 2003 Report Share Posted January 10, 2003 umm...gotta love new error messages. [pwolfe1@TECH04 pwolfe1]$ fluxspace Traceback (most recent call last): File "/usr//bin/fluxspace", line 101, in ? configDOM = xml.dom.minidom.parse(path) File "/usr/lib/python2.2/xml/dom/minidom.py", line 962, in parse return _doparse(pulldom.parse, args, kwargs) File "/usr/lib/python2.2/xml/dom/minidom.py", line 954, in _doparse toktype, rootNode = events.getEvent() File "/usr/lib/python2.2/xml/dom/pulldom.py", line 255, in getEvent self.parser.feed(buf) File "/usr/lib/python2.2/xml/sax/expatreader.py", line 148, in feed self._err_handler.fatalError(exc) File "/usr/lib/python2.2/xml/sax/handler.py", line 38, in fatalError raise exception xml.sax._exceptions.SAXParseException: <unknown>:33:20: not well-formed (invalid token) [pwolfe1@TECH04 pwolfe1]$ Quote Link to comment Share on other sites More sharing options...
tyme Posted January 10, 2003 Author Report Share Posted January 10, 2003 everything likes to default to /usr/local/ instead of /usr but, it doesn't LOOk there...gah. well, glad you guys got it fixed. i still haven't played with it at all.....wonder if it works in waimea? Quote Link to comment Share on other sites More sharing options...
bvc Posted January 11, 2003 Report Share Posted January 11, 2003 It's not fixed....I followed the instructions from Steves email and get the same results Steve does...but I still get the same errors. I tried to edit a few lines in /usr/lib/python-2.2 but (not suprisingly)still no go. I'll email Steve again. If anyone else wants the attachment he sent me (sitecustomize.py) pm me with your email address. Quote Link to comment Share on other sites More sharing options...
bvc Posted January 11, 2003 Report Share Posted January 11, 2003 Man Steve is quick; > Steve, thank you so much for your patience and help! I followed all your> instructions with the install as it was (./configure), and again after > ./configure --prefix=/usr > and get the same result either way. I put sitecustomize.py in > /usr/lib/python2.2 as well. Here's the results Well, based on the error trace below things are installed ok, or at least they're loadable. > Python 2.2.1 (#1, Sep 9 2002, 09:26:21) > [GCC 3.2 (Mandrake Linux 9.0 3.2-1mdk)] on linux-i386 > Type "help", "copyright", "credits" or "license" for more information. > >>> import fluxspace > >>> import sys > >>> print sys.path > ['', '/usr/local/lib/python2.2/site-packages', '/usr/lib/python2.2', > '/usr/lib/python2.2/plat-linux-i386', '/usr/lib/python2.2/lib-tk', > '/usr/lib/python2.2/lib-dynload', '/usr/lib/python2.2/site-packages', > '/usr/lib/python2.2/site-packages/Numeric', > '/usr/lib/python2.2/site-packages/PIL'] This looks fine. > Here's the errors we're getting at startx (X starts, but without > fluxspace) > > Traceceback (most recent call last): > File "/usr/bin/fluxspace", line 101, in ? > configDOM = xml.dom.minidom.parse(path) > File "/usr/lib/python2.2/xml/dom/minidom.py", line 962, in parse > return _doparse(pulldom.parse, args, kwargs) > File "/usr/lib/python2.2/xml/dom/minidom.py", line 954, in _doparse > toktype, rootNode = events.getEvent() > File "/usr/lib/python2.2/xml/dom/pulldom.py", line 255, in getEvent > self.parser.feed(buf) > File "/usr/lib/python2.2/xml/sax/expatreader.py", line 148, in feed > self._err_handler.fatalError(exc) > File "/usr/lib/python2.2/xml/sax/handler.py", line 38, in fatalError > raise exception > xml.sax._exceptions.SAXParseException: <unknown>:33:20: not well-formed > (invalid token) This looks more like an xml parsing error with your ~/.fluxbox/fluxspace.xml. I should improve the error handling so that the messages are more clear. Basically I would guess you have some syntax error in your configuration file. I'd be glad to check the file if you forward it to me. Check it over carefully and compare it to the sample. For getting started you may find it easier to test things out by running fluxspace from an xterm window, rather than starting it with X. At least you'll see the errors immediately in front of you. oops! I just tested my example fluxspace.xml file, and it does have a syntax error on the idesk line. I added that line when I added the idesk module, but didn't test the sample. I do apologize for that oversight. Attached is a new sample that is definitely valid XML. Or just fix the one you have by searching for a backslash ('') and replacing it with a forward slash ('/'). Sorry you wasted time with this. :-) I'll upload a fixed up tarball tonight. Steve IT WORKS!!!!!!! Just change the backslash!!!!!! Whew :shock: :D Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.