GNOME 2.18 released [LWN.net]

GNOME 2.18 released

Posted Mar 15, 2007 2:32 UTC (Thu) by madscientist (subscriber, #16861)
In reply to: GNOME 2.18 released by jwb
Parent article: GNOME 2.18 released

As already discussed, Beagle is not a part of Gnome. I don't know what "bounded runtime" means in terms of Yelp; Yelp is a help file viewer so why does it need to have a "bounded runtime"? As for making gconf faster, do you really expect things like that to be mentioned in the release announcement? They did say there were lots of speedups and efficiency improvements, although I hardly think many Gnome users' lives will be greatly improved by increasing the speed of "gconf --makefile-install-rule" (indeed, I don't even have the gconf program installed on my Ubuntu system).

Personally, I'm pretty happy with Gnome as-is; I'm not looking for some massive reworking. I like Gnome because it does the basics and gets out of my way. What I really, really want to see is some serious work done on bug fixing, stability, memory use and speed, and minor features, especially in productivity apps (in particular Evolution). So, to me, 2.18 looks just fine; I happen to know a bunch of annoying Evolution bugs were fixed (of course these won't be listed in the release announcement), and I'm interested to see the key management improvements as that has also been a bit too haphazard for my taste.

So, bring it on, it looks good to me!

to post comments

GNOME 2.18 released

Posted Mar 15, 2007 2:48 UTC (Thu) by jwb (guest, #15467) [Link] (3 responses)

"... although I hardly think many Gnome users' lives will be greatly improved by increasing the speed of "gconf --makefile-install-rule" (indeed, I don't even have the gconf program installed on my Ubuntu system)."

You might be surprised. gconftool was the chief reason my computer spent over 4 hours upgrading from Ubuntu 6.04 to Ubuntu 6.10*. As for Yelp, it starts more slowly than Firefox, which is really saying something. But my main complaint with it is that it sometimes just runs in a loop eating all CPU, hence unbounded runtime.

Like you, I'm pretty happy with GNOME. You don't see me rushing off to work on gconf or anything like that.

* The other reason was the repeated use of gzip -9 to build the initrd, an operation which takes over 140 seconds on my computer.

GNOME 2.18 released

Posted Mar 15, 2007 3:47 UTC (Thu) by Sutoka (guest, #43890) [Link] (2 responses)

I may be incorrect, but doesn't yelp use the gecko rendering engine, so it
REQUIRES Firefox as a dependency and pretty much embeds firefox? That
would explain why it would start slower than firefox.

GNOME 2.18 released

Posted Mar 15, 2007 6:47 UTC (Thu) by k8to (guest, #15413) [Link] (1 responses)

It uses libxul these days (not sure if ever did differently) to access xul and gecko. At least in my personal experience, some browsers which embed gecko start faster than firefox, so I don't think the layer cake explains things alone.

GNOME 2.18 released

Posted Mar 16, 2007 7:29 UTC (Fri) by drag (guest, #31333) [Link]

I doubt it has anything to do with Gecko or Firefox or anything like that.

I would expect that the problem is I/O related and maybe have to do with XML-based formats.

I would expect that yelp is banging all over your harddrive looking for thousands of little XML files or html files or something like that. Polling this or that directory and trying to build a index of aviable help pages.

I haven't looked at it, but this is generaly why things slow down in Gnome. To many little text files and to many places were they could be and are checked.

Often checked and rechecked and rechecked and rechecked again as application developers often use parts of gnome lib stuff they don't quit 'get'. Or is triggering some hidden functionality that make those lib files are doing something which he didn't nessicarially want.

Also for the other person which had the problem with Ubuntu taking four hours on gconf or something bizzare like that.

I use Gnome on Debian unstable so I regularly get this or that update and I never had anything like that happen with me. Not remotely. So I'm willing to bet that it's something that Ubuntu did to Gnome, not nessicarially something that Gnome did.

There are a few things that Ubuntu does which does odd performance-reducing things.

I noticed that when running 'pure' gnome, as it's designed by the Gnome folks (basicly _no_ firefox, for example. _no_ openoffice.org for another example, but instead epiphany and gnome office) then it's not bad at all.

GNOME 2.18 released

Posted Mar 15, 2007 8:35 UTC (Thu) by spaetz (guest, #32870) [Link] (3 responses)

All people using people but feeling uncomfortable with mono (for whatever reasons) should be looking into "Tracker" an indexer written as part of the Gnome project in C. I've found it to be incredibly fast, use much less memory and already be integrated into Nautilus. There is also a plugin to connect it to the deskbar applet.

It seems to be a fantastic program. BTW, I am not affiliated with that project.

GNOME 2.18 released

Posted Mar 15, 2007 11:17 UTC (Thu) by jospoortvliet (guest, #33164) [Link] (2 responses)

afaik, tracker will be in 2.20, and it's indeed way beyond what beagle
offers in terms of stability and performance.

GNOME 2.18 released

Posted Mar 16, 2007 7:21 UTC (Fri) by drag (guest, #31333) [Link] (1 responses)

Thanks for the tips to the above people.

GNOME 2.18 released

Posted Mar 18, 2007 12:43 UTC (Sun) by drag (guest, #31333) [Link]

I've been playing with tracker and so far when it's running I can't realy tell the difference except for the initial startup.

With Beagle I could get it to work fine if I put certain directories on the 'privacy filter'. My Downloads directory, a directory I used for scratch space and torrents, and a fuse-mounted (sshfs) directory from my file server.

That way it wouldn't try to index the big binaries files and any sort of file that was temporary.

But with tracker I don't need to do this, at least not so far. Although I probably will end up excluding certain directories as I don't want it to clutter up search results.

Beagle made me think that desktop search was just one of those things that only people with relatively new machiens could benifit from. But using tracker I could see people using it quite effectively in in the sorts of machines that already can run KDE/Gnome effectively. Even less then that for people who feel that they could get very positive benifits from having their desktop file indexed.