Date: Thu, 15 Apr 2004 20:44:51 +0200 From: "mark rowlands" <mark.rowlands@mypost.se> To: "Bart Silverstrim" <bsilver@chrononomicon.com> Cc: freebsd-questions@freebsd.org Subject: RE: What happened after gnome upgrade?? Message-ID: <4789E43478F3994BB8D967C73FD9C68850AD@exchsrv1>
next in thread | raw e-mail | index | archive | help
> >> Now with Gnome-2.6 upgraded (mostly OK, crashed ) mostly ok ? ooops! =20 > >> towards the VERY end...), all my things don't work right anymore. > >> All apps like GnomeMeeting, the battery meter, etc appear to be=20 > >> completely messed up. For the most part, they run, but=20 > none of the=20 > >> words, etc are there! The battery meter, when I click on it, only=20 > >> shows the "Do Not Enter" ERROR box, no text and nothing=20 > else visible > >> - again, no words, etc. The same goes for GnomeMeeting. =20 > Also when I=20 > >> try to run the proccess display applet, nothing shows up, just the=20 > >> line graph of CPU usage, but nothing such as process names,=20 > >> descriptions, etc or menu items along the top shows up=20 > anymore. HOW=20 > >> do I fix this?! > > > > GTK+ was updated recently and this sounds like what happens=20 > when apps > > that use it get out of sync with it. You will have to recompile=20 > > everything that uses GTK+. I suggest portupgraded. > > > > /me recently saw this himself with the gtk apps he uses when updated > > gtk+ >=20 > Are you saying that a portupgrade -fRra is required? >From the faq...... >> Oops! I ran portupgrade(1)! What do I do? Do not worry; hope is not lost. Running portupgrade(1) will cause the build to fail, but it will not cause any lasting damage to your ports tree, unless you have done=20 something exceptionally creative. Simply download the gnome_upgrade.sh script and=20 run it, and pretend that you ran it in the first place. Nobody needs to know that=20 you didn't read the directions first! The upgrade failed; what do I do? Unfortunately, this is not only possible, it's highly probable. There are many possible valid GNOME configurations, and even more invalid starting points. If the script fails, follow the instructions in the error message to let the FreeBSD GNOME team know about=20 the failure. The majority of build failures will be dependency-related issues. One simple way to resolve the problem is to remove the offending port, re-run gnome_upgrade.sh, and then reinstall the port when the upgrade process is complete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4789E43478F3994BB8D967C73FD9C68850AD>