Re: Fedora 12 - compiz ruined by updates
- From: Aragorn <aragorn@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 Jun 2010 21:09:15 +0200
On Friday 25 June 2010 17:29 in alt.os.linux, somebody identifying as
I have a home server with Fedora 12 on it. Old hardware:
Pentium III, 800Mhz Coppermine,
400Gb IDE hard drive
FQDN on Comcast cable Internet
Technically, although it may be /old/ in terms of how fast everything
evolves, if the hardware doesn't have any flaws, then I don't see why
you wouldn't hold on to it. After all, most x86-32 GNU/Linux
distributions I know of will run more than happily on such hardware. I
can't think of any that wouldn't, actually. ;-)
It really works great as a server and my desktop is gnome and I like
it a lot.
Just for the record, it is generally advised not to run X11 if you
intend to use the machine as a server, the exception being an LTSP
server of course.
I installed compiz-fusion as one of my first tweaks, loved
it, worked great, everything rocked. I did the updates as they came
along and by maybe the 3rd update, compiz was now broken and I have
not been able to remove or repair it ever since. The desktop has gone
from a usable and very useful tool to a curiosity that is unusable.
Hmm... Are you sure that it's Compiz that's broken? My bet would be on
another component - see farther down.
glxgrears is running great in a term window now, 2390 frames in 5.0
seconds =477.977 FPS. Anything I do that uses compiz will lock up the
computer for about 10-20 seconds until it "recovers" and is then
useless but working again.
Please define "useless but working again"...? If it's useless, then it
cannot be "working again", can it?
Spin the cube, drag a window, anything and I see the "CPU Fire" applet
on the taskbar freeze and I know it is game over. I can "term in" with
putty from my Win7 box and run top to see what is going on when this
Which means that the system itself hasn't frozen, albeit that your X11
session may have. And there could be many reasons for that, but,
again, see farther down.
Here is a snapshot of the top 4 lines in top during a freeze by
attempting to spin the desktop cube.
1725 root 20 0 86988 26m 10m R 39.9 1.8 3:01.98 X
1942 ohmster 20 0 68028 30m 7412 R 30.0 2.0 3:01.09 compiz
2439 ohmster 20 0 36624 7972 2360 R 28.4 0.5 5:31.43 glxgears
2623 ohmster 20 0 2564 1120 828 R 1.3 0.1 0:00.28 top
Word wrap is terrible, I am sorry.
Those are high percentages of CPU time, but not abnormally high.
I was going to show top with only glxgears now with system lock, but
when I tried to move cube, computer is now locked up for good. A hard
reset is all that will work now. Yep, my putty term window is frozen
as well. ...you get the idea.
Always attempt to use the "magic SysRq keys" before pressing the reset
button if you have access to the machine's local console. Userspace
may be locked up, but System Requests are sent straight to the kernel,
and so you may still be able to shut down the machine cleanly.
The desktop is now useless and has been since a month after I
installed Fedora 12.
No one knows how to fix this, nothingI have tried works. The forums
for compiz, fedora, yield no answers, and the best reply I got was
"Send a bug report to Fedora". I tried and if something is not quite
right about the report, you cannot send it. I just did a "sudo yum
update" and everything updated, must be 200 updates including the
kernel, kmod- nvidia, and Xorg, I think. Still my desktop is broken.
That may be the result of the unclean shutdown. Sometimes this leaves
certain configuration files in an incoherent state, even if you have a
I presume you're using ext3 as the filesystem type on this machine -
given that Fedora does not allow you to use any of the other
filesystems - and ext3 has both data and metadata journaling, but the
data journaling is disabled by default. This means that in the event
of an unclean shutdown, the metadata journal will be played back, but
there is still a chance that the crash happened in the middle of a
non-atomic write and that the data itself has gotten corrupted.
I now have the Fedora 13 DVD, will an upgrade install fix this?
I don't really know, because I always prefer doing a clean install
If so, will it just break again at my first system update?
This is always possible, albeit that I don't think this would be the
case. I'm also a faithful believer in "If it isn't broken, don't try
to fix it". Some updates may contain bugfixes and security patches
which you might need, but you surely don't need any fixes for software
you never use. Also bear in mind that updates and upgrades often fix
known bugs by replacing them with unknown ones. ;-)
I dread a clean install as all of my servers, httpd.conf, FTP, alias,
mail settings, dovecot, etc. will all have to be done over again.
Not if you back them up. And if you have an FTP repository, then having
that on a separate partition allows you to save it across
reinstallations, as you don't have to format that partition if you
don't want to.
What is the best way out of this?
I would recommend backing up all your important data - which you should
always do anyway - and doing a fresh install with Fedora 13.
Can or should I just shitcan compiz as not ready for prime time and
give it up?
Compiz *is* ready for prime time. The problem however may be (and
usually is) the proprietary video driver. I strongly suspect that to
be the case.
How can I get rid of it? I tried to uninstall it with yum and thought
I was successful but the problem remains and compiz is still here.
Probably because something else relied upon it, according to your RPM
database. I don't use Fedora myself, but you should check the "man
page" on "yum" for options on how to check for dependencies.
Sorry for the "wordy" post. Please help.
For what it's worth... ;-)
(registered GNU/Linux user #223157)
- Prev by Date: Re: Throw out my parallel port flatbed scanner?
- Next by Date: Re: Fedora 12 - compiz ruined by updates
- Previous by thread: Re: Throw out my parallel port flatbed scanner?
- Next by thread: Re: Fedora 12 - compiz ruined by updates