GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
To be pedantic, not true. Even a "static picture" consumes some CPU time. Whenever you move or resize a window, or minimize or shade, it's that CPU which has to go through the effort of redrawing the wallpaper. This can actually take some serious time on a slower computer with a modest amount of RAM (i.e. the image has been offloaded to swap).
Also, it takes quite a bit of CPU and disk spinning to do a high resolution wallpaper background switch. This causes a definite hit on responsiveness--enough to temporarily disrupt DVD or video clip playback on my workstation.
A constant 4% CPU drain is preferable to an intermittent 50% CPU drain, when it comes to the user's experience. In particular, the timing of this drop in software responsiveness is important. When windows are being moved/resized/closed is when the user is actually "doing something", and this is the worst time for the CPU to be taxed with a slow background refresh.
Surely, you've experience what I'm talking about--you're ready to close one app and go on to another. But when you close your current app the disk starts making busy-busy sounds and the wallpaper background slowly gets redrawn to fill the void...
If you're running gnome or kde, then it's controlling the desktop. You need to kill whatever app is drawing the wallpaper -- nautilus in gnome, not sure what it would be in KDE. There may be another way to do it, but I'm not aware off the top of my head.