Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I started using Linux in the early 90s. I remember installing Slackware from oh so many floppies. When the first CD edition of Slackware came out (1994-1995?) it was such a relief.
Sometime in the late 90s I became adventurous and bought an ABIT BP6 mobo. It had dual CPU support and unbekownest to Intel it had the ability to unlock the overclocking power of the Celeron chip. When set up, my Linux box boasted a 20 MB hard drive, 786 MB of RAM, and dual Celeries churning out a whopping 366 MHZ, each. My window manager of choice was Window Maker. It was, light, very fast, and beautiful.
My job required me to perform a lot of Monte Carlo simulations at home so I had to put together a Windows box, relegating the Celeron box to the background for such mundane jobs as e-mail, IRC, etc. The Celeron box eventually died a natural death, refusing to boot at all.
Years later, having retired from my job, my love for Linux was re-kindled. I installed Ubuntu 12.10 on my quad-core Intel machine, dual booting with Win7. Ubuntu 12.10, being what it is, I downgraded to 12.04 and loaded it with all desktop environments and window managers available (various shades of Gnome, KDE to be uninstalled shortly, mwm, fvwm, fvwm2, fvwm-themes, alpha stage CDE, AfterStep,fluxbox, IRIX look-alike MAXX, etc.) and finally Window Maker. (I remember installing 0.92 but it somehow got upgraded to 0.95.3).
I was quite determined to use Window Maker as my default window manager but there was a problem. When Window Maker started I had mirrored screens on my dual monitors and the Dock did not accept new application icons, displaying only the three default icons. The solution was arandr: Downloaded and installed, arandr quickly arranged the displays but when Window Maker was re-started the displays reverted to the mirrored state.
I've Googled for days to no avail. The solution, again, was arandr itself. It could save the display settings in an sh file in ~/.screenlayout. But how to pass the execute sh file command to Window Maker? So, I put the command in ~/GNUStep/Library/WindowMaker/autostart file and Voila! Window Maker came alive almost exactly as I wanted it to be, Almost, because the Dock was still on the right edge of the primary monitor while I wanted it to be on the right edge of the secondary monitor. Right click on the desktop, Session, then Restart Window Maker solves this problem but, contrary to what I want, it has to be performed manually. Apparently, the "Restart Window Maker" command is an internal command and it seems it cannot be passed to Window Maker from outside. Oh well, I am still happy with my Window Maker even though I have to do the right click thing after it starts.
So, any help with the right click problem will be greatly appreciated.
One possible solution would be to use a .xsession file instead of logging into windowmaker directly. Your .xsession file could contain just your arandr command followed by "wmaker" to launch window maker.
Have you tried using xrandr directly?
You have not given details of the capabilities of your displays and what outputs they appear on, but this is the command I use on my netbook for enabling an external monitor when in Windowmaker.