HEADS UP: GNOME 2.14 being merged into the tree

Vladimir Grebenschikov vova at fbsd.ru
Mon May 1 19:32:08 UTC 2006

В пн, 01/05/2006 в 12:20 -0400, Joe Marcus Clarke пишет:
> On Mon, 2006-05-01 at 17:15 +0200, Michael Nottebrock wrote:
> > michael johnson schrieb:
> > 
> > >> ahze@ seems to have fixed the note in UPDATING for it, although I'm not
> > >> sure it's enough. At least x11/kdelibs wants mDNSResponder, and if
> > >> avahi is already installed the dependencies will be recorded
> > >> incorrectly. I've already informed kde@
> > > 
> > > 
> > > We're working on a fix. Either we will disable mDNSResponder in avahi
> > 
> > Yes, please.
> > 
> > > or hopefully kde@ will want to use avahi's mDNSResponder.
> > 
> > This wouldn't help the people running into the CONFLICTS right now (the
> > dependencies are already registered in people's pkgdbs when they do,
> > changing the kdelibs port won't fix that). We can try to make that work
> > later.
> > 
> > Also ... seriously, do you guys even check just what is depending on the
> > things you're setting CONFLICTS with? I really was not expecting to see
> > anybody pull a fam->gamin again so soon.
> We tested this change as we do all GNOME development versions.  In the
> past, GNOME/KDE conflicts were quickly brought to light by our testers.
> It seems that this time around, we did not have anyone trying GNOME 2.14
> with KDE on the same machine.  I was rather shocked myself to learn
> about this and the xpdf/poppler conflict so late.

Both problems was reported before here:

Vladimir Grebenschikov
<vova at fbsd.ru>
vova at fbsd.ru
Jeremy Messenger <mezz7 at cox.net>
Tuc at T-B-O-H <ml at t-b-o-h.net>,
freebsd-gnome at freebsd.org
Re: Suggested mod for
Mon, 20 Mar 2006 12:50:23 +0300

В вс, 19/03/2006 в 11:36 -0600, Jeremy Messenger пишет:
> We will be no longer need gnome_upgradeXXX.sh in the future version
> GNOME. Bless to the ltverhack that fix libtool bug. Upgrade GNOME 2.12
> 2.14 (still in MC) was a lot easier than any previous version, which
> can be done with portupgrade now. About four to five steps to do it.  
> Here's what I did with GNOME 2.12 to 2.14:
>       pkgdb -Ff (need for gst stuff)
>       portupgrade -f -o net/avahi howl-\*
>       portupgrade -a
>       portupgrade -f -o x11/gnome-screensaver xscreensaver-gnome-\*
> The steps might be change if there is any better. Like might be best
> follow UPDATING before do the portupgrade -a.

First of all thanks for good work.

Unfortunately, I've do this upgrade before above suggestion, so I was
forced to find the solution with howl -> avahi by myself.

Also there is one more conflict of this kind:
evinice requires poppler, but poppler conflicts with already installed
===>  Installing for poppler-0.5.1

===>  poppler-0.5.1 conflicts with installed package(s): 

      They install files into the same place.
      Please remove them first with pkg_delete(1).
*** Error code 1

Stop in /usr/ports/graphics/poppler.
*** Error code 1

Anyway, I get several problems after installation:

most important - some applications stops work due to glib/libthread
% gnome-ssh-askpass2 
GTK Accessibility Module initialized
/libexec/ld-elf.so.1: /usr/local/lib/libgthread-2.0.so.0: Undefined
symbol "pthread_getschedparam"
%  nm -a /usr/local/lib/libgthread-2.0.so.0 | fgrep
         U pthread_getschedparam
 but it can be fixed by forced libc_r load:
% env LD_PRELOAD=/usr/lib/libc_r.so gnome-ssh-askpass2
GTK Accessibility Module initialized

Same library problem with gqview application.

Another problem is constantly dieing gnome-panel after execution
Restarting gnome session (with killing X) helps.

Third problem is GDM, if I choose themed local login it just crashed.
Starting /usr/X11R6/libexec/gdmlogin manually it shows:

The greeter version (2.14.0) does not match the daemon version.  You
have probably just upgraded GDM.  Please restart the GDM daemon or the

gdm was upgraded successfully.

There are also minor glitches, like lost session configuration or clock
applet style after upgrade. 

> Cheers,
> Mezz
> On Sun, 19 Mar 2006 10:16:16 -0600, Tuc at T-B-O-H <ml at t-b-o-h.net>
> > Hi,
> >
> > During STAGE 2 you are portupgrading all of the external
> > The
> > problem I have is sometimes some of what it wants to upgrade are
> > that either aren't as simple as a "portupgrade" (perl for example)
> > things that I don't care to be on the bleeding edge of (nvidia
> > drivers).
> >
> > What I personally did to stop it was wrote the ${external_list} to a
> > temp file, invoke vi on the file, and then feed a cat of that to the
> > run_portupgrade.
> >
> > I was wondering if maybe in the future something like this might be
> > added. Right now my file has 153 items in it to start, and after I
> > pulled out everything I didn't think or want to be upgraded it ended
> > up to be 124 items. I'm not sure a "Do you want to upgrade
> > (Y/N)"
> > would be appropriate, so not sure the best way to go about it.
> >
> >             Thanks, Tuc
Vladimir B. Grebenschikov
vova at fbsd.ru

> Joe

Vladimir B. Grebenschikov
vova at fbsd.ru

More information about the freebsd-gnome mailing list