SlackwareThis Forum is for the discussion of Slackware Linux.
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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
For some reason the compiz that comes in -current doesn't include `kde-window-manager` executable script.
I've re-compiled the program (same tarball from src/ dir) using the exact same configure flags as in Slacks build script and I do get the kde-window-manager script. I'm in fact using compiz right now, rather than beryl.. (I wanted to see if I could get the composite WM that is included to work, because I don't have anything better to do, so I might as well test too see what works in -current)
So, I've grep'ed my way through all of the slackware x/ and kde/ build scripts in -current. there is no mention of "kde-window-manager" in any of them (let alone removing it), and I am now wondering if anyone can point me in the right direction to find out where the differences are?
Where did the file go in Slackwares build?
I imagine this could be a bug, but I don't want to bug any Slack Devs with it until I know the what/where/why of the problem...
Maybe I just had a bad package... re-checking md5sums as I type (dang! none failed).
Last edited by truthfatal; 03-22-2007 at 02:06 PM.
I know, the problem is that even though the default package is built with KDE enabled, it doesn't include kde-window-decorator, which is required for compiz to work on KDE. I just want to know where/when/why kde-window-decorator disappeared from the original package, because building my own package using the exact same configure --flags does build and properly include kde-window-decorator.
compiz is at least as much important as the libc
Last edited by truthfatal; 03-25-2007 at 08:59 PM.