Since a couple of "yaourt -Syu" ago I've noticed that Compiz freezes Gnome. I mean, I can move the mouse and switch (Ctrl+Alt+F1) to a console (in order to kill gdm), but any other input to the desktop environment doesn't work, e.g. can't move, resize, close windows, input any text, launch new apps, etc.
If I kill gdm and login to Gnome again it runs without a window manager and there I can launch metacity or openbox and run without problems. But the moment I run fusion-icon it freezes again. So, it's compiz related.
Edit: PC is Athlon XP2 with Nvidia 7200 graphic card, proprietary drivers.
Last edited by pendor (2011-04-16 00:51:07)
This is no consolation, but I've had the exact same problem. I gave up and went with KDE and kwin. I had the problem before I ever used yaourt, it was a stock install.
Registered Linux user #436067
It's really no consolation, cause I don't like KDE... This thing is getting on my nerves...
Check your logs. It is probably the best place to start when trying to debug problems.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
While running gnome with metacity, you could try issuing '/usr/bin/compiz ccp --replace' from a terminal and watch for any errors printed.
If you are using gdm you should also have an ~/.xsession-errors file, maybe it contains useful messages.
If you started having this problem simply after a package upgrade then check /var/log/pacman.log and see what was upgraded recently. Pay attention to relevant packages ( xorg or compiz or nvidia drivers or gnome...) and maybe try to downgrade. Hopefully you can remember the date you started having the problem and can then identify which of these packages was upgraded that day by checking pacman.log.
Last edited by manmachine (2011-04-10 15:55:47)
The errors I can see in xsession-errors are Murrina related (most of them, quite a lot), or Gstreamer-CRITICAL, or some Nautilus warnings, and a Python exception (from Killswitch.py).
These don't appear to be the cause of the weird freeze...
"/usr/bin/compiz ccp --replace" causes the inmediate freeze with no error message in the launching terminal.
Which other log files should I check?
Edit: compositing works within Enlightenment, so it seems a Gnome only problem...
Last edited by pendor (2011-04-10 16:35:35)
Perhaps there is some info on /var/log/Xorg.0.log or /var/log/messages, also check dmesg (command).
It's hard to troubleshoot stuff without any error messages to hint at the problem.
If you are pretty confident that an upgrade broke gnome/compiz you could try to locate previous package versions stored in /var/cache/pacman/pkg/ and try to downgrade.
Which package to downgrade? I would guess xorg or nvidia drivers. (compiz/gnome have no updates for the past months I think). But do search the wiki or forums first for downgrade instructions if not familiar with the process.
There's nothing in those files that gives me a clue.
And about downgrading, I think I'd rather wait until Gnome 3 comes out of [testing].
Thanks anyway everybody.
Solved the problem on my box. I had the latest Nvidia drivers, which were the problem. I downgraded to the previous version and all is well. Hope it helps.
Registered Linux user #436067
Well, changing to nouveau was (obviouosly, as the latest front page news hinted) the solution...
could you post your 20-nouveau.conf and 10-monitor.conf
because i think mines are not correct
when i launch compiz screen is upside down and left to right oO
My 20-nouveau.conf is:
Got NO 10-monitor.conf in /etc/X11/xorg.conf.d!
My monitor is an AOC 2216Sw, by the way.