Koda

About: I am a digital artist and computer geek with interests in Linux, open source design programs, and saving the world. You will find me blogging here about art, life, technology, and other mildly amusing things. More »

Howto: Compiz, XGL on Ubuntu for the morbidly lazy

Compiz

Last Updated: Jun 8, 2006
Want a more up-to-date compiz? Read a follow-up here.

Overview

Goal: Install Compiz and Xgl on top of Gnome or KDE.

Pros:

  • No compiling, all packages downloaded from Ubuntu repositories.
  • Userspace compiz startup configuration.
  • Works with both fglrx/ATI and Nvidia cards.
  • Cooler X functionality, more responsive GUI.
  • Impress your friends.
  • You know you’ve been aching to try it.

Cons:

  • Recommended dist-upgrade to Dapper.
  • Requires proprietary 3d acceleration drivers, reasonable card.
  • Beta and somewhat buggy software.
  • Video playback issues (mostly on ATI cards).
  • Getting your feet wet.

An Oh-So-Skippable Intro

Compiz.
Maybe you’ve heard the buzz, the pictures and videos, and spent the past few weeks in absolute agony over the coolness of it all. Okay, maybe you haven’t - but I have. I could rant on and on about why this is the absolute coolest thing ever. An OpenGL powered desktop, Composite, OSX-rivalling effects, and works on ATI cards? At first I thought it to be too good to be true. Yet, there are the screenshots, the forum posts, and everywhere people seem to be talking about it. So why not give it a shot?

The problem is, I’m lazy. I don’t want to dirty up /opt/, don’t want to cvs X.org, don’t want to hack anything I’ll have to remove later. So when the first round of make-filled instructions came out, I waited. If you’re a little less excited than I am, perhaps you’re thinking of waiting a while until it’s working in Dapper. Here’s the thing: thanks to a few brave souls, it already is. What?! you say? Okay, it’s quite beta, but that’s part of the fun, right? And you won’t have to compile anything, so it’s like beta without the beta. In just 3 steps, we can do it.

That’s not so bad, is it?

One last thing before we start playing: please do not hold me responsible for any possible side effects you may experience from using this tutorial. Remember, often more can be learned from what breaks in the beginning than what works the first time.

The Real Stuff

Note: I will not cover installing proprietary 3d acceleration drivers within the scope of this tutorial, and assume you have them installed already. If you do not have acceleration set up before following this Howto, your Xgl performance will probably be too slow to be usable. However, installing these drivers is quite easy, only requiring a few extra packages and possibly a configuration change. Consult the Ubuntu website and wiki for information on installing nvidia-glx or fglrx.

Step 1.

Let’s add dapper sources to apt. If you are of the ones already running it, move to step two. Otherwise, just throw this line in /etc/apt/sources.list/:

deb http://archive.ubuntu.com/ubuntu/ dapper main universe restricted multiverse

apt-get update, apt-get dist-upgrade, and you’re good to go. As has been mentioned in some feedback, this can take a long time, especially for those without very fast connections. However, I would reccomend it for this tutorial. My main man Exdaix reports that trying to pull down the compiz package on breezy ended up pulling down a lot of dapper packages anyway… so be cool like him, and dist-upgrade. X-D

Step 2.

Let’s pull down some new stuff. Since around February 15, everything you need should be in two packages. Ubuntu has now split the compiz window manager components into separate packages. Depending on your desktop environment, add compiz-gnome or compiz-kde to this list. Open a terminal, and…

apt-get install xserver-xgl compiz (compiz-gnome or compiz-kde here)

Okay! Compiz and everything we need is installed.

Step 3.

Now, everything we need is ready. We just have to invoke it. My technique of preference is to stick everything in userspace scripts, rather than create symlinks or modify gdm.conf-custom. I do this because (like before) I’m lazy, and would rather not make system-wide changes if I don’t have to. So, open your favorite text editor. Throw this little passage in ~/.Xsession (and create if necessary):

(Credit for the original version of this script goes to http://doc.gwos.org/index.php/Installxgl.)

Note: I have an ATI card. If you are using Nvidia, try replacing Xgl :1 -fullscreen -ac -accel xv -accel glx:pbuffer & with:

Xgl :1 -fullscreen -ac -accel xv:fdo -accel glx:pbuffer &

If you want to run KDE, try replacing gnome-window-decorator with kde-window-decorator, and exec gnome-session with exec startkde.

#!/bin/sh
# Start up Xgl, compiz, and GNOME

# Run Xgl server on :1, on top of normal X
Xgl :1 -fullscreen -ac -accel xv -accel glx:pbuffer &

# Tell subsequent X programs to access the Xgl server at :1
DISPLAY=:1

# Start Compiz window manager
gnome-window-decorator &
compiz gconf decoration wobbly fade minimize cube rotate zoom scale move resize place menu switcher &

# Start GNOME
exec gnome-session

Now make sure it’s +x’d/executable:

chmod +x ~/.Xsession

We have now set up your user X session to start the Xgl acceleration on top of regular X, initialize compiz, and then start GNOME in the new GL-groovified layer. Do note that since GNOME is running on top of our Xgl layer, GNOME and your desktop applications will be running on the Xgl display :1 instead of the usual :0.

Try ‘Er Out!

Let’s see if what we did worked. Now cross your fingers, clamp your eyes shut, and reverently whisper “gui acceleration.” Yes, you’ll have to close this Howto. Try to hold back the tears, however hard that may be. Here’s what we’ll do. In just a moment, log out of GNOME. Then open that menu at the bottom left and change the session: make sure you’ve selected the default session setting, so that our .Xsession file is run.

But wait, where’s my fallback plan? What if things go wrong? If anything breaks or starts acting scary, just close down, reboot, or somehow intervene. If you wish to undo, simply go back to GDM and change the session to “Failsafe Gnome.” The .Xsession file responsible for initializing the Xgl layer should not run, and you can delete it in the comfort of your gui environment. In the worst case, you can log into single user mode from grub and delete the file there. I include this because I know it’s no fun to be left with a non-functioning X configuration without knowing how to undo it - only because I’ve been there so many times. This is not rocket science, but it *should not* torch your system. However, know that there are lots of options.

If things work, you’ll see a checkerboard pattern come up on login, followed by a blue background. The gnome splash screen will then fade and wobble in with the most rockin’ graphics you’ve ever seen. Come right back here and I’ll show you what you can do with your new bling machine. Now, go do it! May the geforce be with you, and all that. :-D

It Worked!

Hurrah! It’s play time. Now, here’s the deal. In the GNOME “Configuration Editor,” (or gconf-editor), you can start tinkering with all of compiz’s options at runtime. Point gconf-editor to /apps/compiz and start messing around. There are tons of little gems hidden inside of compiz’s configuration structure. On a side note, if you are running GNOME, it is reccomended to disable /apps/panel/global/enable_animations. This will turn off the panel “zoom effect” when clicking launchers, which has been known to slow down and possibly crash compiz. Thanks to micampe.it for this information.

There are a few really cool things you’ll notice for starters. Dragging windows makes them wobbly. To make them stick like in the demonstration video, press Ctrl while dragging. Alt-Tab is enhanced by compiz, and will make your windows transparent and fade as you switch through them. F12 is an Expose clone, scaling all your windows to fit in the screen. Dragging the desktop with Ctrl and Alt held down will rotate the desktop to another workspace. Very cool! You’ll notice that non-responding apps will turn to grayscale, as demonstrated in the video as well.

Additional Resources

The Ubuntu wiki has their own Xgl Howto, which provides another method to achieving Xgl and compiz desktop effects. The Gentoo Wiki Xgl Howto provides a wealth of tweaks and information relevant to any distro. Also, for some good details and troubleshooting information, see their section on Xorg and X11 Transparency.

Known Issues

Video playback experiences vary with Xgl. Workaround: for mplayer users, adding the command line arguments -zoom -vo x11 should give reasonable performance at large window sizes. Adding -hardframedrop to the mix can also help prevent audio sync issues (at the cost of framerate) at sizes too large for your system to smoothly handle.

GNOME panel launch square / zoom effect- resolved. See in the above section. If you experience this annoyance, disable /apps/panel/global/enable_animations in the gconf editor.

[chromakode]

Categories: Kode/Linux • Kode/Linux/Howtos
POSTED BY chromakode ON 02.16.06 @ 8:52 pm |

53 Comments »

The URI to TrackBack this entry: trackback.

  1. I’m about to try this… you break something you die. :P

    Comment by Exdaix — February 17, 2006 @ 12:19 pm

  2. Ok, I got it working after re-installing my nvidia drivers/glx and my restricted kernel modules, although I don’t know if that was necessary. I now have wonderful eye candy!

    Comment by Exdaix — February 17, 2006 @ 4:43 pm

  3. This worked for me (still quite crashy), but I had to add LD_PRELOAD=/usr/share/fglrx/diversions/libGL.so.1.2.

    Comment by Michele — February 19, 2006 @ 8:57 am

  4. Wow, I’m so excited right now, can’t wait to see this in action - if only the dist-upgrade wouldn’t take so long. Oh, and I tried to just skip the betas and wait for an 1.0 release or something like that, but this 3-step-howto is just too tempting :-)

    Comment by Felix — February 19, 2006 @ 9:45 am

  5. Hey Michele, thanks for posting your results. Interesting, I wasn’t aware that Mesa was being used for part of the rendering. I also am curious why I didn’t experience this problem in my install.

    I believe the reason is that Ubuntu tacks a library loader onto compiz: /usr/bin/compiz is a shell script that loads the nvidia or fglrx libraries, and then calls /usr/bin/compiz.real. The compiz script ends up doing a LD_PRELOAD=/usr/lib/fglrx/libGL.so.1.2.xlibmesa on my system. Is this the culprit?

    I see on your blog entry that you mentioned the way to disable those panel zoom effects too… I’ll update the entry with this information and credit :)

    Comment by chromakode — February 19, 2006 @ 10:40 am

  6. I’m installing it right now (upgrade is long indeed :P)… But does anybody know the minimum system specs ? I haven’t got the latest-out-of-package-ultra-fast graphic card and gigs of ram, so i expect it all to be quite slow ; i’ll post how it works as soon as it finishes installing (if it works !) ; it would be nice if some ppl could tell their system specs and report how smoothly does xgl run on their machine…

    Comment by Paul — February 19, 2006 @ 4:51 pm

  7. Hi Paul, yeah - the upgrade is a long one the first time around. I would very much appreciate hearing feedback on how it goes! No idea about any “official” minimum specs. I’m running on a laptop here; P4 (HT) 2.8ghz, 512mb of ram, and a Radeon 9600 graphics card. I experience quite reasonable performance, though my specs are on the mid-higher end of the spectrum. However, I also run on a widescreen 1680x1050 resolution. I would expect that on lower resoutions (and resultingly smaller textures), the overall system load is lower. :)

    Comment by chromakode — February 19, 2006 @ 7:06 pm

  8. I’m such a dumbass, i fucked it up ; i forgot step 2 , note it’s 5 am here so i’m a bit tired…

    Comment by Paul — February 19, 2006 @ 8:18 pm

  9. Sorry to hear that, Paul. Hope you’ve managed to get some sleep in the meantime :)
    Remember, you can always disable the compiz and Xgl parts by changing to a “Failsafe Gnome” or regular Gnome session in GDM. If you’re having trouble getting into GDM, that’s another story. Let me know if you need any help getting things working.

    Comment by chromakode — February 21, 2006 @ 3:32 pm

  10. I don’t know, maybe the problem is that I forgot Ubuntu already had the fglrx driver in their packages and I built mine from the installer. That could probably be the problem with my frequent locks, I’ll try again with Ubuntu’s fglrx packages and see.

    Comment by Michele — February 22, 2006 @ 1:01 am

  11. Awesome, it works! Should’ve found this guide earlier, then I wouldn’t be wasting my time downloading and compiling from the cvs.

    Comment by roarus — March 5, 2006 @ 9:32 am

  12. WOW thnx a lot for that tutorial…. it works (with a few little bugs) but i just love it.

    Comment by kennz — March 7, 2006 @ 9:32 am

  13. Hi. I’ve tasted this tutorial but it seems that it dowsn’t works with my card (Intel 855GM). When I start Xgl the windows looks with strange colors and patterns. There is a different way I should invoke Xgl ? Any ideas? THX

    Comment by benn — March 13, 2006 @ 11:56 pm

  14. Hey benn,
    Ouch. I’ve heard of similar reports, but honestly I have very little experience with acceleration the intel chips. Do you have DRI set up? I would suggest trying invoking Xgl with the “Nvidia” command line arguments if you haven’t already. I’ve also read that you might possibly need a CVS version of the intel X.org drivers. Anyway, I’m sorry if this isn’t so much help… good luck in your troubleshooting :)

    Comment by chromakode — March 15, 2006 @ 6:32 pm

  15. mmmm, all i got is a black screen and the mouse pointer here… maybe my Radeon9200 is a bit old, or what could it be the problem?

    Comment by Joel — March 16, 2006 @ 1:48 pm

  16. Hi Joel,
    From the looks of your blog, you might have gotten XGL/compiz working through another means. However, a black screen with a working mouse pointer might mean gnome-session or kde isn’t starting up, or perhaps a problem with XGL. One thing to check would be to run Xgl as a window inside a normal GNOME session. Try just running a Xgl :1 -ac -accel xv:pbuffer -accel glx:pbuffer in a terminal in a normal Session. I believe this should work if your normal X.org is configured correctly.

    Comment by chromakode — March 17, 2006 @ 10:37 am

  17. It couldn’t have been made simpler. Thanks!
    Works on 855GM card, though a little slow.

    Comment by ajitomatix — April 15, 2006 @ 2:51 pm

  18. Glad you’ve had a good experience getting it working. Have fun! :)

    Comment by chromakode — April 15, 2006 @ 4:24 pm

  19. works a charm!! and it’s fast too on a dell dimension 8300 2.6Ghz and 1 GB of RAM. It runs an ATI 9800 pro. your HOWTO rocks!! :]

    Comment by hegenious — April 18, 2006 @ 8:55 am

  20. can i see your gdm.conf and xorg.conf to see if any different between yours and mine, cause i don’t see any change on my desktop. i’m using ATI 9200 card with ATI/fglrx.

    Thanks

    Comment by dedenf — April 20, 2006 @ 7:18 pm

  21. Thanks hegenious - I’m pleased to hear it works for you. It’s a good thing you’ve got 1GB of ram… I’m sure that will help out with the your performance. :D

    Comment by chromakode — April 24, 2006 @ 7:03 pm

  22. chromakode, you are a genious. I was looking at an XGL howto the other day, and decided against it. Too much work for a spot of eyecandy and draggging windows around. Then I read your howto earlier today. I mean, how could I resist? A how-to for the morbidly lazy? You might as well have mentioned me by name :)

    Anyhow, this stuff works great! I now have windows that act like jello, and the really cool desktop changing feature I was looking for in the first place. I used to have it in a third-party application that took a screenshot, launched a full-screen 3d process, and used shots for sides in a cube. Slow and not too impressive. This stuff, this rules.

    Thank you for showing me the way :)

    Comment by Willy André Bergstrøm — May 3, 2006 @ 3:12 pm

  23. Willy-
    I would like to thank you for your kind and wholly heartening comment. Recieving it now has helped brighten my day a bit :)

    Haha, so you too have experienced the somewhat-choppy toy that is “3ddesktop.” I’m glad to hear you’ve found success in getting compiz working. Perhaps while you’re on a roll, you might be interested in reading a little follow-up post I wrote a few days ago regarding installing the cvs version of Compiz via 3rd party ubuntu packages. As you seem to enjoy that cube workspace switcher, I thought of it because this new version has a feature for cross-workspace window dragging. There’s a lot of nice fun other improvements, too (version 0.0.2 to 0.0.10).

    …and remember, it’s not simply morbidly lazy, it’s morbidly efficient ;)

    Have fun!
    –Chromakode

    Comment by chromakode — May 3, 2006 @ 3:49 pm

  24. Awesome howto - I’m now in with some very nice 3d graphics, and all kinds of eye-candy that may not make me work any better, but does look undeniably cool.

    From looking around the ubuntu forums, I’ve also had a play with some other bits and bobs to improve my xgl experience:

    brightside & xte (from xautomation) let me set up the desktop so throwing the mouse in the top right-hand corner does the clever Alt-F12 thing and shows all the windows, and xbindkeys along with transset-df gives the alt-mouse-wheel to change window transparency dynamically (it didn’t work on mine before). Still toying with whether to go for the cvs version, or stay slightly off the bleeding edge.

    thanks again

    Comment by Gwilym — May 4, 2006 @ 8:37 am

  25. I’ve tested four differend guides to do this and this is the first to work! Little bugs and slowness around here and there, but what’s to be expected from a program at beta stage.

    Comment by Leevi — June 3, 2006 @ 6:15 am

  26. Dapper

    I upgraded from Breezy to Dapper today. It went pretty well except for a couple of things - GNOME wouldn’t start up, and emacs has a weird error. I could log in from GDM, but the splash screen didn’t come up and nothing but my desktop bac…

    Trackback by Eugene's Weblog — June 12, 2006 @ 4:06 pm

  27. “Work’, but no kde window decoration =/ (and compiz-kde installed)

    Comment by Derek — June 18, 2006 @ 1:17 pm

  28. Wow, it worked pretty, “out-of-the-box” ! Thanks for your help !

    Comment by Roberto Valle — June 21, 2006 @ 4:41 pm

  29. I’ve followed your very simple tutorial as well as I can, but I keep coming across this single error whether I’m trying to boot Xgl, or if I run it from the tutorial. I’m using an Nvidia card on gnome. I keep getting this error:
    Couldn’t open RGB_DB ‘/usr/share/X11/rgb’

    Fatal server error:
    no visual format found

    Have any idea what that means? Thanks in advance.

    Comment by Chris — June 26, 2006 @ 5:33 pm

  30. Thanx for the howto. I guess it worked. Is this the normal behavior: My apps open and stick to the upper LH corner. They don’t resize or move in the work space. I can rotate the cube but not being able to move the windows around makes it unusable.

    Comment by tuco — June 28, 2006 @ 9:41 pm

  31. XGL is 3D for the sake of it, the usability is crap and the novelty soon wears, not worth using. 3D desktops so far are just gimmicks it would be nice if they added some innovative 3D features that benefit usability.

    Comment by foo — July 2, 2006 @ 12:07 pm

  32. Well, I would love some gimmicks ;-) I just can’t get it to work. Have gotten 3d to work:

    ~$ fglrxinfo
    display: :0.0 screen: 0
    OpenGL vendor string: ATI Technologies Inc.
    OpenGL renderer string: MOBILITY/RADEON 9000 DDR Generic
    OpenGL version string: 1.3.1072 (X4.3.0-8.25.18)

    But it seems like compiz is not getting a “composite extension”. The Gnome looks the same. I have earlier followed the instructions of other how-tos, but the closest I have got is a Gnome-like desktop wthout the window borders. Strange.

    I guess it is hard for you to tell from my fumbling descriptions what might be wrong.

    Comment by Hans — July 5, 2006 @ 5:50 am

  33. Chris: I’m not sure about the cause of that problem, though I have encountered it before. It sounds to me like it could be an issue with your version of X11/XGL — perhaps try some of the updated packages referenced in this follow-up howto. Beyond that, as with most problems, the best I could reccommend would be to google for it… :)

    Comment by chromakode — July 5, 2006 @ 3:51 pm

  34. tuco — sounds like gnome-window-decorator (or kde-window-decorator) is not getting started, or XGL is working but compiz isn’t running. What I would try would be to open a terminal on startup and try running them manually. You’ll be able to see error output and better assess the problem from there.

    Comment by chromakode — July 5, 2006 @ 4:01 pm

  35. foo: I respect your opinion regarding the usability of the current 3D desktops. Certainly the tradeoff between better desktop usability versus hardware requirements is not very persuasive. I am also concerned about the issues with reliance on technology that creates dependency on non-free 3D hardware drviers.

    However, I must say that I find a few of compiz’s features to be quite important to my daily usage. One of the most notable ones is instant screen magnification. You’d never think of it as being useful beyond those with vision issues — but I actually find myself relying upon it several times a day! As a digital artist and a person who likes to share things with others on-screen, I can’t emphasize how valuable it is to have the instant magnification. :)

    Comment by chromakode — July 5, 2006 @ 4:10 pm

  36. Thanks for the tutorial! Works like a charm but now some of my openGL games do not work right - namely Foobillards. Not that it matters much. The balls turn white and flicker when it is my turn to shoot. Could it something in my xorg,conf? Oh - I’m using an Nvidia card if that matters.

    Comment by EJ — July 5, 2006 @ 6:07 pm

  37. Hans: it sounds to me like compiz itself may not be running. In my experience when XGL is working but compiz isn’t, you get the desktop without window borders. You also will notice the XGL gray and white launch pattern flash during startup. This would also make sense since your GL sounds like it’s working. Try running the compiz command from your .Xsession file on a terminal where you can watch the output (during the windowless desktop). I’d guess that for some reason compiz is erroring on startup…

    Good luck. :)

    Comment by chromakode — July 5, 2006 @ 6:27 pm

  38. Thanks for your reply. Yes it seems like the driver for my ATI mobility radeon 9000 that I thought I finally had sorted out don’t work after all. fglrxinfo returns a lot of lines like “[fglrx] API ERROR: could not register entrypoint for IsFramebufferEXT”. Call me lazy, but as a noob that have already used hours to figure this out, I think I will give up.

    Comment by Hans — July 5, 2006 @ 10:53 pm

  39. Thanks for the tutorial man. BTW, I’ve got a few things to talk about with the plugin. Some ppl are leaving comments and want to know a few things. I’ve been kind of busy but I’m ready to start again. Hit me up when you get a chance.

    Comment by Chris — August 6, 2006 @ 7:56 am

  40. When I try to log back in with default session setting, GDM gives me “the greater application appears to be crashing. attempting to use a different one” every time I try to log in as default. Did I slip up somewhere?

    Comment by Alex Watkins — August 20, 2006 @ 6:23 am

  41. Alex —
    Gotcha. I would guess that there is a problem in your .Xsession file — perhaps a typo or a command that is not being found. I’d try running it manually from your “Failsafe Terminal” session option (”./Xsession”). Hope this helps! :)

    Comment by chromakode — August 21, 2006 @ 12:52 pm

  42. [quote]The balls turn white and flicker when it is my turn to shoot.[/quote]

    Tee-hee-hee!!

    Comment by Gabriel Crowe — September 11, 2006 @ 8:12 am

  43. Thanks for the How-to.

    Comment by Krishna Kumar — September 15, 2006 @ 10:46 pm

  44. Awesome HowTo. For months, I’d been looking in vain all over the web for an easy-to-follow and working HowTo for XGL/Compiz. Yours was the only one that fit that criteria.

    One thing I will say, though: when I pasted your text into my ~/.Xsession file, “rotate zoom scale move resize place menu switcher &” appeared on a separate second line from “compiz gconf decoration wobbly fade minimize cube,” so I was unable to resize windows, have window decorations appear, or Alt-Tab between applications.

    If anyone else is having that problem, you should fix the ~/.Xsession file and until you reboot add those items to gconf-editor > apps > compiz > general (key, not folder)

    Comment by aysiu — September 30, 2006 @ 4:50 am

  45. i cant seem to get it to work… maby im a moron. when i try to log in i get the the error: unable to exicute binary file.

    Comment by ryan — October 2, 2006 @ 6:24 pm

  46. Aysiu: Glad to hear this was helpful for you. Thanks for letting me know the line breaks on that code snippet are acting funny. I’ve always been torn between the kind of counter-intuitive indenting you see currently and an ugly horizontal scrollbar for these wide lines.

    I believe in the compiz-quinn variants and more current incarnations of compiz, the gconf plugin specifies the plugins used, and they’re no longer needed on the command line — though you should still have gconf (ala “compiz gconf”). This howto is really starting to show it’s age, and I am close to phasing it out in preference to one of the emergent forum howtos on installing Beryl at http://forum.beryl-project.org/. If you haven’t checked Beryl out, I highly recommend it. Good luck with your compiz tinkerings!

    Comment by chromakode — October 3, 2006 @ 8:37 pm

  47. ryan —
    That is a pretty strange error to get on login. I would recommend to check ~/.Xsession and make sure it’s got executable permissions first, but since you’re saying it reports “unable to execute binary file,” that suggests to me that permissions are fine and something strange is going on with the file. Definitely make sure your ~/.Xsession is a sane bash script first, though after that, it’s not obvious to me what file in particular could be the problem. I’d guess that you’ve either got a corrupt executable or a script filled with gobbledygook somewhere. If you get any further troubleshooting and need a second opinion, I’d be happy to see if I can help.

    Comment by chromakode — October 3, 2006 @ 8:43 pm

  48. I try this,

    *********************************************************
    If anyone else is having that problem, you should fix the ~/.Xsession file and until you reboot add those items to gconf-editor > apps > compiz > general (key, not folder)
    *********************************************************

    but there is not a folder compiz > general to put the key.

    Any Ideas?

    Comment by axllaruse — December 18, 2006 @ 10:27 pm

  49. These comments have been invaluable to me as is this whole site. I thank you for your comment.

    Comment by Rosie — April 28, 2007 @ 9:22 am

  50. everytime i do this and restart the machine it gives me a eeror that says somthin is wrong with the x sever. Also it wont load ubuntu back up to its orginal screen it just gives me a text screen where i can enter my user name and password then a command prompt apears idk whats goin on any sugestions?

    Comment by mike — August 15, 2007 @ 5:39 am

  51. i cant seem to get it to work… maby im a moron. when i try to log in i get the the error: unable to exicute binary file.

    Comment by oyunlar — August 28, 2008 @ 11:41 am

  52. Very nice,easy to follow howto.
    I think I have made it work but it is really slow although my system is C2Duo E6300,2gb Ram,ATI x1600 ultimate.

    Please someone tell me what can cause that sort of situation…

    Comment by Kadir — September 22, 2008 @ 6:53 pm

  53. thansk you all

    Comment by kız oyunları — October 6, 2008 @ 2:03 am

RSS feed for comments on this post.

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>