Just a friendly reminder – 2.19.3 is due to be released before midnight UTC, today. 
(Come on, this is supposed to be fun for volunteers, isn’t it? You know I love you guys.)
On a related note, GARNOME 2.19.3 has just been rolled and is available at a mirror near you.
We are pleased to announce the release of GARNOME 2.17.3 — ahead of the official GNOME release, which is expected to be announced soon (read hours). After constant updating, tweaking and testing, especially the last 2 days, the actual release was smooth and quickly done.
Get the code while it’s hot, and fix (ok, or report) bugs before anyone else does. Get the love now!
Dave, you are so right, xsnow is a great app for the holiday season (as is my “special” music CD dated 1994, but that would be a different story).
I first saw this years ago on my account in a Sparc Station pool. We have been limited to using OLVWM, but the admins where kind enough to add xsnow by default to the session early Dec. Nice surprise. I quickly got that for my own machines…
However, you probably do recall correctly, and there is an issue with running xsnow on a GNOME Desktop. At least it has been last time I checked. The issue is, that the snowflakes properly work with the background image, but cause “severe damage” to the icons on your Desktop. A snowflake falling right through these icons leave a trail behind, re-rendering the background image, instead of the icon. Just a couple of minutes, and you won’t see any icon unless you “wipe off the snow” with the mouse or, even better, a larg-ish window.
I spent some time hacking a custom version (2 years ago?), implementing some code from xpenguins. It kind of worked, and supported command line tweaking, but anything close to a smooth re-rendering appearance really hogged my CPU.
From your screenshot, it looks like there are no Desktop icons. So that would be the reason, why it now “works” for you running GNOME, I guess. Or maybe there finally *is* a fix? I need to check that… 
(Unfortunately you still won’t see this on p.g.o, so I am going to poke you on IRC instead.)
Never announce while you are waiting for others to roll a tarball. Lesson learned.
There are already a couple of updates and fixes in CVS, so we plan to roll 2.16.2.1 on Monday, releasing additional love to our users. Currently waiting for another Evolution tarball that fixes a bunch of leaks. Official tarballs with fixes are always preferable over patching the sources ourselfs.
Also pending, some test builds…
If all these “pretty looking girl”s who are sending me mail daily really would come to my place like they promised, I’d need some of these advertised “mens pills”. And I can afford them, cause I sure take advice from a complete stranger with low spelling abilities who knows about the finest penny stocks taking off soon. But please, no more Rolex replica offers or member enlargement devices — the girls find me attractive just as I am.
That’s what you get when you can’t sleep, and instead decide to check the low scoring Spam mails for false positives. On the plus side, I now do know that my hand tweaked SA is catching 400+ Spams a day, and doesn’t catch even a single good mail. Yay…
So I have been staying away from Bugzilla for a whole week apparently. Didn’t really realize, but I dropped off of the weekly stats entirely.
Almost felt like vacation. A constant rate of a thousand bugs per week for a couple of weeks really burned me out. But I feel like I should get back to Bugzilla again. Already started by processing that huge pile of backlogged Bugzilla spam. There’s a lot work awaiting me…
On another note, the GARNOME Team already is planning a new release, 2.16.2.1, which probably will be out later this week. Dot two already included a lot of serious crash, leak and security fixes. Some more have been released the days after the official GNOME release — and we always try to provide the best vanilla flavored distribution.
It’s always nice to help out fellow Bugsquad members and help them find the proper duplicate if they are unsure. Get 4 bug numbers, a short description — and start checking the reports and some related facts in FTP and CVS.
A couple of minutes later you nailed down the original report together. Effectively closing one report as duplicate, adding a good stacktrace (which the fellow bug hunter already got by reproducing the crash) with debugging symbols to the original bug stuck in NEEDINFO — and even know another already closed bug that probably is the same issue.
This holds true especially if the “fellow bug hunter” happens to be one of those rare women in this male dominated part of the world.
I still remember her from her very first bug day, initiated by #gnome-women. And coincidentially I noticed her yesterday in the weekly stats, place 4 bug closer. Way to go, Susana!
A blog. No, my blog. Yay. Now I am important, no?
Seriously, I meant do do this for a long time already. Get me a place where I can drop some thoughts of mine, and maybe have the public read it. As opposed to the IRC way of doing this — keep writing the same stuff over and over again. A personal homepage you say? Nah, that’s so 90’s. Been there, done that, got the t-shirt. In fact, I set up more than one homepage, or at least worked on it locally. But lost interest when it got to constantly maintaining it — developing is so much more fun than to just update it. So I ended up with dropping them sooner or later. Let’s see how this works out.
Of course I got my blog at gnome.org, rather than one of these, err, anonymous blog sites, where every random Joe can register such a thing. I got it here as part of the community.
What to expect? Not sure yet. Thoughts about GNOME related stuff. Yes. Maybe some personal matters. Politics? Sure not. What else… Well, we’ll see.
First, I need a target audience. Or rather, I need to reach my target audience. What’s a blog good for, if no one reads it? Oh, wait — personal review of one’s experiences, just as a diary. Will I do this?
Speaking of the audience — I want to be syndicated at Planet GNOME. Getting this blog was a pretty nice experience, and extremely fast. Thanks O.! Now let’s see how long it takes to get on p.g.o. Seems to be a good way to spread ones my opinion. Thus, I’ll probably not blog about most things currently concerning me, until I got there. No audience, no fun.
Bad Behavior has blocked 13 access attempts in the last 7 days.