SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I installed compiz, and when I try to run it
$compiz
compiz: Another window manager is already running on screen: 0
compiz: Another window manager is already running on screen: 1
compiz: No manageable screens found on display :0.0
Did you go through the post installation configuration on the compiz website? It helps. I had a similar problem. Basically, you need to add <compiz --replace> in the program start-up list.
on a fairly stock slack 12 the magic phrase used on my machine to start compiz is
...
compiz --loose-binding --replace ccp &
kde-window-decorator --replace &
....
i think the --replace is what is giving you problems
i think it allows the replacement of the current window manager
hope this helps
John
After all this, add "compiz --replace" to Desktop -> Preferences -> Sessions -> Startup Programs. Save the file and restart 'X' by pressing Alt+Ctrl+Bksp. Even after this if you have problems, reinstall it. I doubt if you have installed it correctly.
What sounds me strange is you're saying "installed" about compiz. It comes from x packages serie on a "stock" Slackware 12.
Anyway fluxbox is a window manager not a "full" desktop environment such as KDE or Gnome (coming with their own WMs).
Compiz is a Wm too (plus a window decorator). So I don't believe you'll get compiz working on fluxbox for the reason that it will be replaced as soon as compiz starts.
Hope this helps
Ciao
Last edited by urka58; 01-04-2008 at 12:34 PM.
Reason: a missing "W"
Don't know if it's related to your particular scenario but I got the same sort of error when I compiled a new kernel and forgot to include the Direct Rendering Manager for my particular graphics.
This is an example of boilerplate that does work...
nvidia-xconfig --composite
...FTW!
Also useful to know about:
--use-events - enables a bit of stuff in the newer drivers that makes XvMC "go faster" (affects CPU usage during video playback of HIGH-bitrate files) but may potentially cause "halty" animations or intermittent freezing of the display. Don't use this (or invert it with --no-use-events) unless video playback of really high bit-rate video (like 1080p or digital TV) video is a higher priority than spinny cubes for you. You have been warned.
...oh, and --no-logo.
Bits one probably doesn't need with the latest drivers:
--add-argb-glx-visuals - Needed for 9xxx and some earlier 100.x.x drivers (before 100.14.19 if my notes are correct).
--render-accel - should be the default behaviour (since 9746) so you can probably leave it out.
--damage-events - should improve performance involving GLX with composite enabled in much the same way UseEvents improves video playback, but may backfire or not work with older drivers. Reportedly does not work with SLI configurations (but I don't think my spinning cube needs that much power). 100.14.19 made this the default so you probably don't need this bit either.
--disable-glx-root-clipping - might be needed, but only for 100.x.x drivers older than 100.14.19. Guess when it was made the default.
If you don't have an nVidia card with the nVidia driver, then none of this applies to you. Also, may the gods have mercy on your soul.
Boilerplate is only useful when you explain why each thing is or is not needed, because otherwise, you're generally as likely to send someone spinning off in the wrong direction as you are to helping them. Particularly worthy of mentioning are that most of those things listed as probably not needed are things that, beyond a certain driver revision, are handled automatically (and correctly) by the driver. If someone lobs a bunch of stuff into their xorg.conf, then has a problem and goes to flipping these things on or off, they'll definitely be going in the wrong direction.
...but still, guessing is not useful, particularly when things are so terribly far from the actual problem, which was that the user just wasn't starting Compiz properly. "'A' for effort" translates into "send the user spinning off on time-wasting tangents", and the first respondent already nailed the actual problem.
(Yes, I've been following this stuff for awhile, and while I do have even the latest version running without a problem at home, getting Compiz-Fusion working usefully/stably for anyone but nVidia users is still a huge pain in the butt.)
Last edited by evilDagmar; 01-05-2008 at 12:31 PM.
(Yes, I've been following this stuff for awhile, and while I do have even the latest version running without a problem at home, getting Compiz-Fusion working usefully/stably for anyone but nVidia users is still a huge pain in the butt.)
--add-argb-glx-visuals - Needed for 9xxx and some earlier 100.x.x drivers (before 100.14.19 if my notes are correct).
This only works by default only on new Xorg servers.
I doubt that adding Option "AddARGBGLXVisuals" "true" to xorg.conf even when using the latest and greatest will make the system unable to startx. Anyway, you can always create a backup just in case.
Last edited by Alien_Hominid; 01-05-2008 at 01:22 PM.
It doesn't much matter since if the guy isn't using Slackware 12, then he's had plenty of time to say so by now. ...and that option does not pose any problems for the current version of Slackware.
For that matter, Compiz didn't ship with any older versions of Slackware, and do versions of Xorg that don't support that even have the potential to reasonably run Compiz?
:/
Last edited by evilDagmar; 01-06-2008 at 01:45 AM.
Compositing managers require AIGLX. AIGLX was included in Xorg 7.1. Slackware 12 has 7.2 (if I'm not wrong). So actually Xorg 7.1 can run compiz. OP has Fedora 8.
BTW, I'm still at 6.8 (no Compiz there). I'm just wondering why with each Xorg release my fps drop down lower and lower. I don't have sufficient knowledge about the graphics subsystem to get the answer myself. So if anoyne has a clue, please post your reply.
Last edited by Alien_Hominid; 01-06-2008 at 05:53 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.