Gnome 2.22.0

Message

EvaSDK · Post by **EvaSDK** » Wed Jun 11, 2008 2:48 pm

MalleRIM wrote:The updated of libgweather to 2.22.1.1 breaks the linkage of gnome-applets against it. gnome-applets can't be recompiled, it exits with a failure. I tried both paludis and portage, with and without ccache. I'll try using different versions of libgewather and gnome-applets.
This is the error message:
[/code]

edit: gnome-applets-2.22.1 work

What about 2.22.2 ?

bertaboy · Post by **bertaboy** » Wed Jun 11, 2008 4:19 pm

At the risk of being annoying and sounding stupid, but....

Does anyone know what the progress of HAL is?

MalleRIM · Post by **MalleRIM** » Wed Jun 11, 2008 4:40 pm

EvaSDK wrote:What about 2.22.2 ?

I haven't tried it

blueflame · Post by **blueflame** » Thu Jun 12, 2008 10:47 am

EvaSDK wrote:
blueflame wrote:Anyone notice that Nautilus no longer preserves a file's modification date & time when you copy it?

I wish developers would not mess with established features and behaviors of such fundamental parts of Gnome.
yes this is a known bug and has already been reported upstream.

Excellent news!

Thank you.

terracotta_shore · Post by **terracotta_shore** » Fri Jun 13, 2008 7:21 am

blueflame wrote:
EvaSDK wrote:yes this is a known bug and has already been reported upstream.
Excellent news!

blueflame, you look more cheerful about this than I feel. This issue is being referred to as a 'bug', but that is not the word I would choose to describe it. Perhaps 'shambles' or 'cock-up' would be nearer the mark. Why am I so severe? It's not because there's a bug. Bugs happen; that's life. It's because three months after Gnome 2.22 was released upstream there is still no 'official' fix in sight. I've already posted a link to this Gnome bugzilla bug on another thread, but I thought it would be useful to put it up again. This bug was opened four months ago. Now look at the date and text of comment #32 (the latest at the time of this post). And comment #30 expresses better than I can why I am so upset about all this:

I can't believe it, that is bug is still only marked as Normal. It should be
marked a show-stopper. Just have a look around, which operating system, modern
or old have this behavior. And please imagine hundreds of thousands users
copying the data without knowing that the date-time information is lost on
their valuable historical data.

Yes, this 'bug' destroys data and in such a way that the data owner may not realise until it is too late.

OK. Rant nearly over.

This Ubuntu Bugzilla thread makes fascinating reading. Look at one of the 2008-06-11 comments, that any 'official' fix is "already too late". An interesting point of view.

blueflame · Post by **blueflame** » Fri Jun 13, 2008 7:44 am

Ok, yeah I agree it is a cock-up. But I'm encouraged that a Gentoo Developer views it as a bug, which means (hopefully) Gnome 2.22 will not be placed into the portage stable branch until it's fixed. Maybe I'm being too optimistic

Desperadoss · Post by **Desperadoss** » Thu Jun 19, 2008 6:43 am

really good news thanx !

GODLiKE · Post by **GODLiKE** » Wed Jul 02, 2008 1:25 am

After upgrading to Gnome 2.22 everything but the volume control ran smoothly. I have a SB Live! 5.1 card and I had XF86AudioLower/RaiseVolume bound to several volume controls (Master, Wave, Wave Center, Wave LFE and Wave Surround). That way I could control the volume for all my channels from my keyboard without much hassle.

Since the upgrade to 2.22, my keyboard only lowers or raises the Master channel, even when I specifically set it to control the other ones in gnome-sound-properties. The odd thing is that even when I set no channel to control there, my keyboard still controls the Master channel.

From the gnome mixer applet I can still control the channels together with the slider, although when I set them all to zero and try to raise them again, the master channel stays muted. Also, my mute button on the keyboard only works in (again) the Master channel.

Anyone had a similar problem and knows how to fix it/debug it? I really wouldn't like to downgrade to 2.20

MalleRIM · Post by **MalleRIM** » Wed Jul 02, 2008 8:57 am

Right click on the volume applet and choose "Properties". Set the Channel to be controlled to PCM. PCM changes the volume of all output channels for me but they can still be changed individually.

GODLiKE · Post by **GODLiKE** » Wed Jul 02, 2008 10:42 am

That only changes the channels you control through the mixer applet, which work perfectly fine except for that zero bug I mentioned before. Besides on my Live, PCM only seems to affect the front channels. I just want to change several channels from my keyboard like before, and not only the Master

.

juniper · Post by **juniper** » Sat Jul 05, 2008 11:39 pm

blueflame wrote:Ok, yeah I agree it is a cock-up. But I'm encouraged that a Gentoo Developer views it as a bug, which means (hopefully) Gnome 2.22 will not be placed into the portage stable branch until it's fixed. Maybe I'm being too optimistic

isn't this an upstream problem. Will it be fixed in the 2.22 series? by that I mean, if it is an upstream gnome problem, will they fix it for the 2.22 release, or will 2.22 remain unstable forever?

mottmar · Post by **mottmar** » Sun Jul 20, 2008 5:56 pm

Ok this is a little weird... I liked a lot the new "weather" feature in the 2.22 clock applet. Before that I was using the separate weather applet. Now what is strange is that the weather icon/temp doesn't show up anymore. I tried rebuilding gnome-applets and revdep-rebuild'ed, but nothing happened. I reverted to the weather applet, which works flawlessly. Any clue?
PS: I know that there are many issues more serious than this, but it was one of my favourite "new toys" in 2.22...

rahulthewall · Post by **rahulthewall** » Thu Jul 24, 2008 10:21 pm

mottmar wrote:Ok this is a little weird... I liked a lot the new "weather" feature in the 2.22 clock applet. Before that I was using the separate weather applet. Now what is strange is that the weather icon/temp doesn't show up anymore. I tried rebuilding gnome-applets and revdep-rebuild'ed, but nothing happened. I reverted to the weather applet, which works flawlessly. Any clue?
PS: I know that there are many issues more serious than this, but it was one of my favourite "new toys" in 2.22...

Strange, it works for me.

On another issue, do not intend to be cocky, but is 2.22 going stable or are we waiting for 2.24?

Wojtek_ · Post by **Wojtek_** » Fri Jul 25, 2008 12:46 am

Seems like we'll have to move from 2.20 straight to 2.24...

Kasumi_Ninja · Post by **Kasumi_Ninja** » Fri Jul 25, 2008 9:11 pm

Leio wrote:Ok, so here's a big reply on some of the stuff in here up to now.
...

Regarding gnome-base/gnome-2.22.0 and gnome-base/gnome-light-2.22.0 meta packages:
Learn to use your tools and especially emerge. emerge --upgrade --deep --verbose --ask gnome (or rather emerge -uDva gnome) will work with 2.20 meta ebuilds too... nothing in the 2.20 meta tells that it's restricted to gnome 2.20 packages. This way you will just not get new modules (cheese and vinagre) forced on you yet, and will have a redundant gnome-keyring-manager still pulled in. That's it. Other than that you can have a full GNOME from that. This is why we do not pay any attention to the metas in the overlay, and therefore none get updated for a new version before everything is in portage and it's almost ready for unmasking. It's just not necessary.

Regarding taking ages to get into the tree:
GNOME-2.22 includes a full rewrite of the virtual filesystem, nautilus is rewritten in that area, lots of other things use it via glib-2.16's GIO now. It has had many problems, starting from not working functionality, and ending with it wiping your $HOME (yes, your home directory) as late as in release candidates when you happen to want to restore something from trash (fixed now..). Are you sure you wanted that in portage as soon as possible? Things are looking very good now, thanks to many cherry-picked patches and testing and we are near to unmasking.
Please note that KDE4 is still hardmasked and will remain so until KDE4.1 comes out in a few months, so I'm not sure where the comparison can be drawn.

So, patience is a virtue and packages likely breaking your system are tried to be kept in p.mask and overlays.
This time around a new GNOME is not in portage immediately on release due to actual big problems with it from upstream (and that's cool, the new virtual filesystem rocks after the bugs are almost worked out by now when we are getting close to 2.22.1), instead of lack of quick work on it from our part, so that's much much better compared to earlier two big releases. Thank you for your understanding and support.

Great, now I know why the latest Gnome is still masked. In a (distro) world where everyone strive to have the latest bleeding edge packages included, sometime looks like Gentoo is lagging behind. Having read this thread (and testing Gnome 2.22 myself) I know better now and instead I wonder why does every distro ship with Gnome 2.2 (or KDE 4 for that matter)

uaeb · Post by **uaeb** » Fri Jul 25, 2008 10:02 pm

Aniruddha wrote:Great, now I know why the latest Gnome is still masked. In a (distro) world where everyone strive to have the latest bleeding edge packages included, sometime looks like Gentoo is lagging behind. Having read this thread (and testing Gnome 2.22 myself) I know better now and instead I wonder why does every distro ship with Gnome 2.2 (or KDE 4 for that matter)

Because it's what the people want or perhaps the devs of those distros feel that pushing it out will force upstream to re-think and re-work. Thankfully the Gentoo devs have some sense and know when to hold back.

Kasumi_Ninja · Post by **Kasumi_Ninja** » Fri Jul 25, 2008 10:28 pm

uaeb wrote:
Aniruddha wrote:Great, now I know why the latest Gnome is still masked. In a (distro) world where everyone strive to have the latest bleeding edge packages included, sometime looks like Gentoo is lagging behind. Having read this thread (and testing Gnome 2.22 myself) I know better now and instead I wonder why does every distro ship with Gnome 2.2 (or KDE 4 for that matter)
Because it's what the people want or perhaps the devs of those distros feel that pushing it out will force upstream to re-think and re-work. Thankfully the Gentoo devs have some sense and know when to hold back.

Yeah I think it's better to choose yourself if you want to go bleeding edge. At least now I know why some of the major distro's are problematic an erratic in their behavior (because of the inclusion of software that isn't mature yet). I more and more appreciate the 'release it when it's stable' philosophy of Debian/BSD/Gentoo/Slackware.

MalleRIM · Post by **MalleRIM** » Sun Jul 27, 2008 8:14 pm

yay, amd64 stable! thank you so much, Olivier Crête!

MM23 · Post by **MM23** » Sun Jul 27, 2008 9:14 pm

oh lord it's stable now

time for a million icon compatibility issues, woo!

Kasumi_Ninja · Post by **Kasumi_Ninja** » Sun Jul 27, 2008 9:20 pm

MalleRIM wrote:yay, amd64 stable! thank you so much, Olivier Crête!

Lol, why is amd64 only stable?

MM23 · Post by **MM23** » Mon Jul 28, 2008 2:53 am

because we're so much cooler than you

Post by **Leio** » Mon Jul 28, 2008 3:56 am

juniper wrote:
blueflame wrote:Ok, yeah I agree it is a cock-up. But I'm encouraged that a Gentoo Developer views it as a bug, which means (hopefully) Gnome 2.22 will not be placed into the portage stable branch until it's fixed. Maybe I'm being too optimistic
isn't this an upstream problem. Will it be fixed in the 2.22 series? by that I mean, if it is an upstream gnome problem, will they fix it for the 2.22 release, or will 2.22 remain unstable forever?

This [nautilus copying loosing mtime] had been fixed with a patch in nautilus-2.22.3-r1 since 29th of June, and upstream since 2.22.4 (30th June). nautilus-2.22.5.1 is what's going stable.

Aniruddha wrote:Lol, why is amd64 only stable?

Because an amd64 arch team member was able to promptly, after CCing of arch teams on the stabilization bug, work on it thanks to being free over the weekend, and other arch teams will follow when they are able to. Stabilizing GNOME requires a few hours of free time slice for arch teams.

Post by **Leio** » Mon Jul 28, 2008 4:01 am

Aniruddha wrote:Yeah I think it's better to choose yourself if you want to go bleeding edge. At least now I know why some of the major distro's are problematic an erratic in their behavior (because of the inclusion of software that isn't mature yet). I more and more appreciate the 'release it when it's stable' philosophy of Debian/BSD/Gentoo/Slackware.

And you can use ~arch if you want to choose the bleeding edge

Kasumi_Ninja · Post by **Kasumi_Ninja** » Mon Jul 28, 2008 7:30 am

Leio wrote:
Aniruddha wrote:Yeah I think it's better to choose yourself if you want to go bleeding edge. At least now I know why some of the major distro's are problematic an erratic in their behavior (because of the inclusion of software that isn't mature yet). I more and more appreciate the 'release it when it's stable' philosophy of Debian/BSD/Gentoo/Slackware.
And you can use ~arch if you want to choose the bleeding edge

Sst, don't say that too loud. I've seen horrible problems wit ~x86 of which users tend to blame Gentoo

Post by **Leio** » Mon Jul 28, 2008 4:48 pm

Aniruddha wrote:
Leio wrote:And you can use ~arch if you want to choose the bleeding edge
Sst, don't say that too loud. I've seen horrible problems wit ~x86 of which users tend to blame Gentoo

That's (among other things) the "bleeding" in bleeding edge upstream software

Gnome 2.22.0

clock applet weather info missing

Re: clock applet weather info missing