Re: GNOME 2.91.4 build issues

[Vincent Untz <vuntz gnome org>]

Le vendredi 24 décembre 2010, à 01:33 +0100, Vincent Untz a écrit :
> Le jeudi 23 décembre 2010, à 20:01 +0100, Vincent Untz a écrit :
> >  + latest empathy doesn't build with latest gnome-keyring:
> > gcr-simple-certificate.c:122:1: error: conflicting types for ‘gcr_simple_certificate_new’
> > /gnome/releases/usr/include/gcr-3/gcr/gcr-simple-certificate.h:57:21: note: previous declaration of ‘gcr_simple_certificate_new’ was here
> >    Apparently, some code was pasted from gnome-keyring and since they
> >    share the same prefix...
> 
> Not fixed. Potential blocker.

Guillaume fixed this, and will release a new tarball. Thanks!

> >  + interestingly, when there's no icon theme set by g-s-d, metacity goes
> >    crazy with:
> > metacity:ERROR:ui/ui.c:752:meta_ui_get_default_window_icon: assertion failed: (default_icon)
> 
> Not fixed, but not a blocker. Will file a bug tomorrow.

https://bugzilla.gnome.org/show_bug.cgi?id=637933

>   + GNOME Shell doesn't start if you don't have introspection from
>     gnome-bluetooth. I guess it could survive this. But no big deal.

https://bugzilla.gnome.org/show_bug.cgi?id=637935

>   + gnome-settings-daemon crashes if the media-keys plugin is enabled
>     (which is the case by default). Disabling it in gsettings works.

https://bugzilla.gnome.org/show_bug.cgi?id=637936

>   + after login, the wallpaper is drawn after a few seconds, and then
>     becomes black. It's fine again if I start nautilus. I'm not sure
>     what is to blame here (g-s or g-s-d?)

Lateness might be https://bugzilla.gnome.org/show_bug.cgi?id=568385

Black bacground is https://bugzilla.gnome.org/show_bug.cgi?id=637938

>   + probably a theming issue: tabs are not drawn where they should be.
>     They're drawn something like 50px or 100px below.

https://bugzilla.gnome.org/show_bug.cgi?id=637940

>   + GtkSpinButtons don't have the "down" arrow, and make the app crash
>     if I try to use the "up" arrow. I quickly looked at the stack trace,
>     and it looked like it was possibly related to the theming engine.

Missing arrow: https://bugzilla.gnome.org/show_bug.cgi?id=637942

Crash: https://bugzilla.gnome.org/show_bug.cgi?id=637943
(filed against GTK+ since there's no product for
gtk-theme-engine-clearlooks)

>   + there's a general issue with starting launchers: most (all?) don't
>     work in gnome-shell, and if I go to $prefix/share/applications in
>     nautilus, I can't launch them either. I've no idea why this is
>     happening, though, and it could well be a local issue.

Not filed yet, need to investigate what's going on.

>   + dconf-editor crashes when I go in /desktop/gnome/interface

https://bugzilla.gnome.org/show_bug.cgi?id=637944

I also filed:

  + lock settings don't get saved
    https://bugzilla.gnome.org/show_bug.cgi?id=637939

  + system information panel is hardcoded
    https://bugzilla.gnome.org/show_bug.cgi?id=637941

And I might file more later...

FWIW, at the moment, I consider the theming issues, the g-s-d issue and
the crash in GtkSpinButton as blockers.

Vincent

-- 
Les gens heureux ne sont pas pressés.