Ubuntu :: Compiz Fails To Start With A Possible Bug
Aug 31, 2010
I have been using compiz on my laptop loaded with Lucid,without any problems.Recently i reinstalled lucid but now i dont have a compositing manager, I try
I have a geforce 8400GS and nvidia-current installed. However, the Additional Drivers app advises that "No proprietary drivers are in use on this system" and that the driver is activated but not in use. I know other people have complained about this problem, but for me this is breaking 3D content and I can't get compiz to work either. When I try to start compiz manually (compiz --replace), I get this error:
Code: compiz (code) - Fatal: Couldn't open display My Xorg has nvidia as device driver. I'm using the NVIDIA X Server settings program to setup my two monitors, so I know that this is what is in use. In addition to the compiz problem (which I can get over), sometimes I can see the desktop background through the active window. It's hard to explain so I'll take a screenshot when it happens again. Things I've tried:
1. Installing nvidia's latest drivers - The installer was extremely picky, constantly complaining about other modules and drivers. After I finally managed to remove everything it didn't like and install it, X wouldn't load.
2. Reinstall nvidia-current - tried multiple times with no change.
3. Link /usr/lib/xorg/modules/extensions/libglx.so to /usr/lib/nvidia-current/xorg/libglx.so.270.41.06 - didn't make a difference.
When I turned on my computer today, Compiz would not start. I tried launching it from the terminal, and this is what I got:
Code: joseph@joseph:~$ compiz --replace Checking for Xgl: not present. xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log
A botched ATI proprietary driver upgrade caused a cascade of problems. I've installed this driver many times before, but this time something just went wrong. I may have made a mistake. There don't seem to be many complaints about the ATI 10.2 driver so this seems likely. Anyway things were quite unstable for a while. I had problems with nautilus (lost the desktop) and segfaults from compiz. I had to reinstall a lot of stuff etc etc.
Anyway, this episode has left me with a strange lingering malaise. I can get the machine into a state where everything works perfectly - the cube is fine and quite snappy, the desktop is all there; it looks great; New driver seems to be working OK. But when I log out and log back in there are problems.
Step 1:If compiz is the window manager during login it dies killing the nautilus desktop and leaving me without a window manager running (no window decorations). This is a nasty state to be in because you can't easily get at a terminal (yeah ctl alt F1 - but how to fix the window manager from there). I've got a keyboard shortcut for metacity which lets me recover from this state. But afterwards I can't get the desktop back.
If metacity is the window manager during login - no problem. I've got a desktop. It starts up fine. Everything looks good. But I'm running metacity and I want to run compiz. So now we try to get compiz running.
Step 2: If I enter "compiz -- replace" in a terminal compiz segfaults and doesn't put metacity back leaving me without a window manager again. Just before it segfaults it complains about not finding some expected graphics files. This seems to have something to do with cube caps [Edit=Not - see later]- but I've restored defaults there so ... Fortunately ctrl C gets me out of that and back to metacity. Or I use my shortcut. But gee whiz no compiz.
OK - here is where it gets interesting. If I go to the compiz settings manager and disable the cube, then compiz --replace works just fine. So it looks like something specific to the cube. This lets me get compiz running but without the cube.
Now things get really interesting. Once compiz is running, if I open the compiz settings manager, then I can enable the cube and in fact ... it works!
To sum up, I now have to go through the following procedure every time I log in.
1. Login in with metacity as default window manager 2. Disable the cube in compiz settings manager 3. Start compiz with compiz --replace 4. Enable the cube in compiz settings manager.
After doing that everything works fine ... at least until I log out.
The fact that I can get everything to work indicates that I've got the driver installed OK and it is working. But why should I have to go through this bizarre procedure each time I log in?
Notes: 1. The problem afflicts all users - so it probably isn't a user config file issue. 2. I've reinstalled compiz and a whole lot of xwindows stuff. Didn't help. 3. I will try downgrading the video driver to the previous version as a last resort. But if the problem is something I broke while things were messed up, downgrading the driver may not fix it. 4. I'll post the crash message compiz generates in a followup (I'll have to log out and back in to generate the crash so I can copy the message)
I have been customizing my 10.10 NBR to my personal liking.I have already disabled the default Unity "experience" and enabled Gnome.However I have hit a bit of a tough spot with Compiz. It will install, and it appears I enable it in the Visual Effects menu, but I do not think it actually is enables and once I close the dialog it reverts back to the "none" option in Visual Effects.What I dont understand is that Compiz worked fine on 9.10 NBR.I would just give up, but I really want window previews with the Talika plugin.My netbook is a Acer Aspire One D150.
I'm a Karmic user, using a Nvidia Geforce 9500GT video Card.
I'm telling you about my GPU, because since I upgraded to the 190.42 Nvidia "official" new drivers, what's happening is:
My Compiz is no more able to save it's configuration across the sessions, and every time I close my PC or when I simply need to restart my active session, Compiz needs to be started again manually, It do not auto-activate by the compiz setting preferences. Doing: System --> Preferences --> gnome-appearance-properties (TAB: "Visual effects") and click on "normal" checkbox, to activate the compiz visual effects.
Is there anyone able to teach me how to save the compiz activation, in order to avoid the manual, boring, repetitive, activation each time?
Well, I initially had quite a lot of trouble getting Compiz to work, but I finally got it to go. I had to use these start-up parameters in order to get it to work: Code: LIBGL_ALWAYS_INDIRECT=true compiz --replace --sm-disable ccp & emerald --replace How in the world do I get Compiz to start up like this on boot up, so I can use it easily?
I've been searching for hours now on how to start compiz from command line and configure the plugins. I just want to use the compiz core package in Slackware (no add-ons for now). I've figured out starting compiz
Code: compiz --replace and the windows decorator
Code: gtk-window-decorator --replace kde-window-decorator --replace for gtk based or kde respectively. I know how to start the plugins (by putting their names in the compiz command), but not what all of their command line names are.
What I'm looking for is all the console names of the base plugins (and eventually the others too), the order they need to be started in (if any), how to automatically start compiz when X starts, and how to change plugin settings (all without ccsm). How to do the above stuff without the use of a graphical tool.
Just upgraded kubuntu to Lucid and found no KDE installed: bad news: if you're on kubuntu KDE should be upgraded automatically. So using kpackagekit in gnome installed the standard metapackage and got the option to log in with KDE (good news) but then KDE failed: segmentation fault in knotify4.it would not report the error: too little information. it dropped me back into an incomplete gnome environment (no top and bottom tool lines).
How to get compiz to auto-start. What seems to be the generally accepted method (from what a few google searches and the debian wiki tell me) of using gconf-editor and changing the window manager from 'gnome-wm' to 'compiz' in desktop > gnome > session > required_components doesn't change anything. The only method I found that did not involve using a terminal and running 'compiz --replace' every time I boot the computer was to add compiz and fusion-icon to the gnome startup apps, but this causes unwanted flickering (it starts metacity and then replaces it with compiz, ie it's simply automating what I would do with the terminal). Autostarting the fusion-icon alone does not start compiz, although it allows me to start it from it's menu if I right click the icon. Note that I sometimes use fluxbox as well, so starting it on boot isn't really an option either.
Perhaps this can be useful : compiz: Installed: 0.8.4-4 Candidate: 0.8.4-4 gnome-session: Installed: 2.30.2-3 Candidate: 2.30.2-3
Ubuntu 9.10 Mono 2.4.2.3 On running; $ mone /path/to/.exe following warning popup:
Code: Fatal Error System.ArgumentOutOfRangeException. Argument is out of range Parameter name: index at System Collections Generic List`1 [System String] get_item (int32 index) [0x00000] at Verse_of_the_Day.MainForm.ctor () [0x00000] at (wrapper remoting-invoke_with-check) Verse of the_Day.MainForm.ctor () at Verse_of_the_Day.English.ReadWrite () [0x0000] I have been searching around and could not find a solution.
I just installed Ubuntu 10.04 fresh and was putting my preferences back in for Firefox and MythTV and such when I noticed Evolution wouldn't start. I would click on it and the cursor would change for about 5 seconds and then nothing. I tried uninstalling Evolution (big mistake), but after I got back into the desktop, Evolution still wouldn't start. I can't seem to find anything around here that deals with this. Where should I start to debug this?
Awhile back I was playing around with Plymouth and GDM resolutions. I followed some wrong instructions and screwed up my GDM. I have fixed my GDM, sorta, but at times it will not start or when it does the login screen has strange pixel errors.
Sometimes it starts fine without any problems or pixel errors. Other times I have to boot 2 to 3 times before GDM will start.
If GDM starts with pixel errors, I can still login to Ubuntu and the rest of the OS runs fine. Pixel errors only happen in GDM.
When GDM fails to start I get a blank black screen. Cannot enter command line. OS seems frozen and I have to reboot.
I'm running desktop Ubuntu 9.10 on my Dell laptop. Previously it was Ubuntu 9.04. After some period of time (lets say 3-4 months) my X fails to start automatically after some restart calls. If that takes place my network manager applet doesn't start either (after I do startx).
I get a perfect server boot meaning there's no Xorg started. Command line interface is all I get starting from login and further.
How to resolve this apache2 problem I keep getting, I have installed a debian LAMP server with ispconfig3 and everytime I reboot apache fails to start, I don't know and I have done some research but nothing seems to work, which leads me to reinstall everything from scratch again, I think I have reinstalled at least 10x or more.
I've got a couple of nagging issues that may or may not be related to each other. First, although I have this machine set to log me on automatically (I'm the only user ever and there's no public access) it doesn't; I get the standard login welcome screen. In the system menu (from Applications) I have two login managers: "Login Screen" and "Login Screen (GDM2)". The first of these shows I'm configured for automatic login, as does the custom.conf file in /etc/gdm. However when I click its "unlock" button, it flashes orange momentarily but nothing else happens. The second manager doesn't seem to have any effect on the problem...
The other issue is that my networking fails to start during boot-up; I'm not using the network manager applet and am not starting it; instead I have the three NICs in the machine (which serves as the router and gateway for my LAN) configured in /etc/network/interfaces. Once I am logged in, I can run "sudo service networking start" from a Terminal window and everything works properly, but adding that same line to /etc/rc.local (minus the "sudo" of course) had no effect on the problem. Both issues happen only at boot time, and since this machine normally runs 24/7 except immediately after certain updates or when troubleshooting they're not show-stoppers, but I greatly prefer to have my systems working the way I've configured them rather than going off in other directions!
I've just updated to 11.04 from 10.10.After restarting desktop does not startIt says [OK] for every command line, but nothing 'graphical' happensOn and other console I tried:
Since about one week, my OpenSuse 11.1 sometimes does not start automatically KDE 3.5 as configured. This failure does not occur every start up, just from time to time.
It stops booting in command line mode telling me:
The last changes i did were installing VMWare Server 2, could this take effect? Does anybody have an idea? Where can I find the boot logfiles?
I've just upgraded to 9.10, and mysql fails to start. When I do an /etc/init.d/mysql start, I just get * Starting MySQL database server mysqld ...fail!with no additional errors or information to say what went wrong. I saw this thread http://ubuntuforums.org/showthread.php?t=1322070 but the fix mentioned does not apply, as I don't have the #skip bsd line in my config file.
My ubuntu server was working normally but it suddenly failed to start, stopping after the following message: init: ureadahead-other main process (587) terminated with status 4 after this message, the system halts and does not finish the start up processes.
If I start the server in recovery mode, I get: init: ureadahead-other main process (587) terminated with status 4 [ 21.892940] ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI region HWMI [0x295-0x296] the system also halts and does not start. Right now, I can not use the server at all.
i have installed ubuntu 9.10 inside windows vista.now when i start my system i get option to select windows or ubuntu. windows can start successfully but ubuntu start up fails and give grub shell prompt as :
I have installed Scilab through the Ubuntu software center. When I try to launch it from the Applications menu it will not start. Same hapens if i try to launch it using alt-F2. But I can launch it using the terminal.