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.

All my efforts to configure compiz in Slackware 12 so far have failed. I either get a very slow and unusable X when I call compiz like this:
LIBGL_ALWAYS_INDIRECT=1 compiz --replace ini decoration wobbly fade minimize cube move place resize rotate scale switcher water zoom &

or I get the errors:
libGL warning: 3D driver claims to not support visual 0x51
compiz: GLX_EXT_texture_from_pixmap is not supported by direct rendering context, trying indirect rendering context instead
compiz: GLX_EXT_texture_from_pixmap is missing
compiz: Failed to manage screen: 0
compiz: No manageable screens found on display :0.

I second WulfNStein's suggestion. While I haven't sorted out reading from my .compiz configs, The docs at the compiz site were spot on with regards to configuring my xorg.conf and with using "ini" all worked just fine.

I second WulfNStein's suggestion. While I haven't sorted out reading from my .compiz configs, The docs at the compiz site were spot on with regards to configuring my xorg.conf and with using "ini" all worked just fine.

I have already read the stickies in those forums concerning configuring compiz. Alas, nothing seems to work properly on my system. I wonder why I could find no documentation about compiz coming with Slackware 12...

Slack ships with Linux How-to's and man pages. Not instructions for near beta eye candy no matter how much fun it might be.

I have added /user/doc to directories scanned by recoll and yet nothing comes out when I type compiz. There is no man page either. Concerning the above link, the "configuring compiz" section includes three links. GConf is not present in Slackware, compiz-setting is no more supported, and I havo no gnome on my system for the third option ...

I get the same problems that tramni1980 has. Decorations disappear, the keyboard get locked along with the Konsole. And I get almost exact error messages.

EDIT: I've added the two commands from the original post to a script and executed the script, it still locks up and I lose the decorations, but Compiz seems to be "working" because the window wobbles when I move it and the cube rotates when I switch between desktops...

All my efforts to configure compiz in Slackware 12 so far have failed. I either get a very slow and unusable X when I call compiz like this:
LIBGL_ALWAYS_INDIRECT=1 compiz --replace ini decoration wobbly fade minimize cube move place resize rotate scale switcher water zoom &

or I get the errors:
libGL warning: 3D driver claims to not support visual 0x51
compiz: GLX_EXT_texture_from_pixmap is not supported by direct rendering context, trying indirect rendering context instead
compiz: GLX_EXT_texture_from_pixmap is missing
compiz: Failed to manage screen: 0
compiz: No manageable screens found on display :0.

EDIT: Those lines can actually hurt more than they help. I was wrong on this point. After much experimentation, I have discovered that the above lines aren't helpful, and may cause a little extra instability. I was wrong. I am sorry for that.

I see you already included the following lines

Code:

Section "Extensions"
Option "Composite" "Enable"
EndSection

. You also need to add the upper lines as well.

I am running compiz on two laptops. Both are equipped with Intel video adapters. One is a less than six months old Compaq with a Celeron M at 1.86 GHz. The other is also a Celeron, but a PIII version at 1.06 GHz. The first one runs it as smooth as silk. The latter runs it, but it's a bit on the ker-chunky side. No matter, it works on both!

One more thing, if you are using a custom compiled kernel, make sure that you set up the video drivers under

Code:

Character devices--->Direct Rendering Manager

as modules. If not, your compiz has no chance of working...at least the install on my other laptop didn't work until I recompiled its kernel as instructed above.

Now it works, albeit slowly.

And as someone said somewhere else, compiz is buggy. It certainly is! There are a few bugs in it that really uh...BUG me, but I have compiz set up so I can turn it on and off at will.

X never falters. KDE never fails to come back up. Anymore than that will come with time, and more dedicated compiz developers, testers, and users becoming allied with the project.

pappy_mcfae, I've tried what you suggested, but I still loose all the borders when I run compiz.

My setup is a laptop with intel dual core processor and an integrated I945 graphics adapter and 2GB od DDR2 ram. Like I mentioned before, compiz worked fine on Fedora Core 6 which I tried earlier, but it seems to have a lot of problems runing on Slack 12.

pappy_mcfae, I've tried what you suggested, but I still loose all the borders when I run compiz.

My setup is a laptop with intel dual core processor and an integrated I945 graphics adapter and 2GB od DDR2 ram. Like I mentioned before, compiz worked fine on Fedora Core 6 which I tried earlier, but it seems to have a lot of problems runing on Slack 12.

My humblest apologies for that. It sure worked with me...and my machines are nowhere near as balls to the wall as the one you describe above.

My new laptop is a 1.86GHz Celeron, and only one Gig of memory...DDR2, as a matter of fact. It is also running the I945 chipset with 128 megs video RAM. It took a while to get all the gears meshing properly, and I spent a lot of time looking around at other threads devoted to compiz.

Finally, I found one that had some information that finally got my compiz up and running. This particular link has a lot of information on compiz as it comes with Slackware 12.

It wasn't until I used the script that tramni1980 provided that I even got close to getting things going. This article is the one that really got things straightened up and (almost) flying right. It is compiz, which means there are a few bugs hanging about. Oh well, I've worked with buggier software. Thanks to 1337ln for the above link.

Be of good cheer. It seems that while compiz doesn't just hop up and work right the first time around, once you do get it to work, it stays working. I can't wait until they get some of the more annoying bugs worked out...like focus.

pappy_mcfae, I've tried what you suggested, but I still loose all the borders when I run compiz.

That means that compiz is actually loading. I was doing some experimenting last night, and I made an interesting discovery. I discovered that for some reason, if you were to set up your compiz command as follows:

Code:

compiz --replace ini <other plugins>

sometimes kde-window-decorator won't start. However, if you were to change it to:

Code:

compiz --replace <other plugins> ini

where the "ini" plugin isn't the first option given after "--replace", then kde-window-decorator works. I forget exactly which document on compiz told me that one, but low and behold if it didn't work for my PII 450MHz.

The point was really moot because compiz runs really, REALLY SLOWLY on that machine. It's sort of pointless to run it on it, but it does actually run.

I am in the middle of writing a howto document for compiz that is distilled from LOTS of other stuff I have read on the topic, as well as my experiments. So, for the time being, I am going to experiment on that machine to see what process is needed to make compiz functional...things like does /etc/X11/xorg.conf really need all those added lines...and what happens if they aren't there.

I'll gladly post my results as soon as they come to pass, in another thread.

2. Second problem is regarding the looks of the decorations, as they get distorted a little. First I noticed a white line going all the way acros the scren on top of the bottom panel. It's about 6 pixels wide. The same white line (this time border) appears around all tooltips and menues.

3. Opening Home, System, Trash or any other directory opens just a partial window with no contents in it (not as if it is emtpy, but as if it is partially loaded).
EDIT: After playin around for a few mintues, the contents of the windows are now ok.

4. One more thing, when I maximize a window, it seem to strech to far (beyond the screen by about 5 pixels)

I guess I'll cut down on the number of plugins and add one by one and see how it goes.