Linked by Eugenia Loli on Thu 8th Sep 2005 16:53 UTC
Gnome The Gnome Project released version 2.12 yesterday. We had a quick look at it by using the latest Gnome Live CD (1.12-pre) and Foresight 0.9.0 (2.12 final) and here are our thoughts over 2.12 and Gnome's status in general.
Thread beginning with comment 28874
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Gnome is overrated...
by on Fri 9th Sep 2005 10:10 UTC in reply to "RE[6]: Gnome is overrated..."

Member since:

As it is, spiffifity simply doesn't work (it would have been better to fork xcompmgr like KDE and start with at least SOMETHING) and that was the reason it was left out of Breezy

The problem is that xcompmgr is as unusable as KDE kompmgr. You have to use all kind of hacks (depending on the setup) to make them work without crashing your entire machine. The only compositor that works reasonnably well is the one used by XFCE. Everything else is just instable, especially if you want to use OpenGL apps and XV videos.
And I use NVidia binary drivers, so I should know. They are still too unstable.

I think Gnome devs rely on EXA to accelerate things for the near term. XAA is really too old and unaccelerated.

Without xcompmgr turned on in Gnome, when my CPU is being maxed out and I move windows they leave behind a very ugly trail. When I minimize apps under the same condition, Metacity leaves blackness on my desktop for a second or two. With xcompmgr turned on, both of those problems go away.

Your setup has a problem, because I never experience any of this without using xcompmgr, even when my 2 CPUs are maxed out. I experience small jerkiness or slowness sometimes with CPU maxed out, which is irritating, but that's all.

I would just leave xcompmgr on but even in Breezy it fights with Gnome some (less than before though)

I don't know what you mean. At home, any compositing fights inside the card or inside the driver. If it was fighting Gnome, I would have no problem using it with XV or GL apps. For now, KDE 3.4.2 still will crash on start with any compositing on. If you have no acceleration without activating compositing, sth is really wrong with your setup. Compositing is not supposed to accelerate anything. With cairo, I know my Nuvola (vector icons) desktop is faster than before, but perhaps it is due to optimisations in GTK+.

I will switch to KDE for 3.5 and leave unaccerated Gnome in my past.

For that, you'll have to hope that compositing works in KDE 3.5. In KDE 3.4.2, it still crashes everything here with a Ti4200 and latest NVidia drivers. For metacity, they disable the compositor by default, and tell you to activate it only for debugging purpose. I think they will improve it. As manufacturers probably won't make a lot of dev to improve their cards, the work will have to be done on kernel DRM, XOrg components and DE compositors. DRM work is the more important part IMHO, as it will manage the state between XV, composite and GL apps.

Reply Parent Score: 0

poofyhairguy Member since:
2005-07-14


The problem is that xcompmgr is as unusable as KDE kompmgr. You have to use all kind of hacks (depending on the setup) to make them work without crashing your entire machine. The only compositor that works reasonnably well is the one used by XFCE. Everything else is just instable, especially if you want to use OpenGL apps and XV videos.
And I use NVidia binary drivers, so I should know. They are still too unstable.


Honestly even XFCE's crashes hardcore on me. The reason I still use Gnome with xcompmgr because I can easily turn it off and on when I need to do something that I CAN'T have crash. I just can't wait for one of the DEs to release a compmgr stable enough I don't need to do that anymore- which ever one does it first has me as a convert. From what I here it will be KDE 3.5. If this is not the case I will be the first to bitch about it. ;)


I think Gnome devs rely on EXA to accelerate things for the near term. XAA is really too old and unaccelerated.


Gnome WILL rely on it, months after its released and KDE does.....Gnome will be fully accerated by it but probably more than a year from now.


Your setup has a problem, because I never experience any of this without using xcompmgr, even when my 2 CPUs are maxed out. I experience small jerkiness or slowness sometimes with CPU maxed out, which is irritating, but that's all.


Seeing as how much I care about UI responsiveness, I bet the truth is I'm just more picky than you. When I use a Mac I don't gasp at Expose and the drop shadows, I gasp when I move windows and the edge lines don't break.


I don't know what you mean. At home, any compositing fights inside the card or inside the driver. If it was fighting Gnome, I would have no problem using it with XV or GL apps.


1. run xcompmgr

2. try to log out in Gnome

3. see what I am talking about

If you have no acceleration without activating compositing, sth is really wrong with your setup. Compositing is not supposed to accelerate anything.

Composting allows my GPU to get in on drawing the desktop. This accerated EVERYTHING- all the things drawn like windows and whatnot. I know because I'm picky and I feel a huge speed difference when I use the

xcompmgr -a

command (the one without all the effects).


With cairo, I know my Nuvola (vector icons) desktop is faster than before, but perhaps it is due to optimisations in GTK+.


Cairo is not hardware accerated yet.

Reply Parent Score: 1