On Sun, 2 Aug 2009 09:08:18 +0100 Thomas Adam <[email protected]> sent this information:
>[ Adding [email protected] back -- please don't go culling the Cc list! ] Apologies - I used Ctrl + L and assumed it would post to the list, didn't check it, but it doesn't work for this list. It returned it to you. >2009/8/2 Charlie <[email protected]>: >> I attempted to run FvwmConsole through my ~/.xsession but that didn't >> work either. Maybe my syntax was wrong. > >No, that won't work because FvwmConsole is a FVWM module -- FVWM has >to spawn it so it can create a pair of pipes to communicate with the >module, broadcast messages to it, etc. I didn't really think it would work, but as mentioned I tried everything I could think of. >> Oh yes, I tried to run it the first few times by clicking on the >> module in fvwmModules, and I also have a fvwmConsole socket in my >> ~/.fvwm/ directory, but still couldn't get it to work. Some other >> module like fvwmDesker work fine. Will try out what you have posted >> above as soon as > >Then it won't have been anything to do with "ModulePath" which is >good. I don't understand though why you can have the socket kicking >around though. That gets removed when FvwmConsole does (i.e., the >module dies.) Are you saying it's *always* present -- even before >starting FvwmConsole? That being the case, remove that socket first. The socket has been present since the first time I tried the module. Did as you said, still didn't work but the socket was back and stayed. >FvwmConsole will try and use xterm by default to provide a console for >you. You *do* have xterm installed, right? If not see the >"-terminal" option to FvwmConsole to perhaps try some other terminal >emulator. I do have xterm and it loads and works. >Until I get some concrete feedback, I'm done clutching at straws for >now. :) > >-- Thomas Adam Thanks Thomas - did the things you suggested in your email, but no joy. I think this is the problem: This from ~/.fvwm-errors: [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/terminal.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/terminal.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/terminal.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/terminal.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/programs.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/system.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/home.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/configuration.xpm [fvwm][scanForPixmap]: <<WARNING>> Couldn't load image from menu/help.xpm and so it goes on into infinity. So it can't find the images and therefore can't load the applications? Maybe that means something to you, I assume I will have to change something so that fvwm can find these images? Hope that helps. I will look for the reference where it's looking for the images - obviously in the wrong place? Thanks again for your time. Charlie -- Registered Linux User:- 329524 +++++++++++++++++++++++++++++++++++ All wisdom is rooted in learning to call things by the right name. When things are properly identified, they fall into natural categories and understanding becomes orderly. .....Confucius >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Debian GNU/Linux - just the best way to create magic
