From owner-freebsd-questions@FreeBSD.ORG Fri Apr 16 05:11:52 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48D4616A4CE for ; Fri, 16 Apr 2004 05:11:52 -0700 (PDT) Received: from mail.boundariez.com (mail.boundariez.com [216.36.108.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC37143D49 for ; Fri, 16 Apr 2004 05:11:51 -0700 (PDT) (envelope-from Ralph@boundariez.com) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 16 Apr 2004 08:06:46 -0400 content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What happened after gnome upgrade?? Thread-Index: AcQi6jbZVOhn8VDmQ6adEw24PWk3sgALwbWgACR46NA= From: "Ralph M. Los" To: "mark rowlands" , "Bart Silverstrim" cc: freebsd-questions@freebsd.org Subject: RE: What happened after gnome upgrade?? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 12:11:52 -0000 ::-----Original Message----- ::From: mark rowlands [mailto:mark.rowlands@mypost.se]=20 ::Sent: Thursday, April 15, 2004 2:45 PM ::To: Bart Silverstrim ::Cc: freebsd-questions@freebsd.org ::Subject: RE: What happened after gnome upgrade?? :: :: ::> >> Now with Gnome-2.6 upgraded (mostly OK, crashed ) :: ::mostly ok ? ooops! ::=20 ::> >> towards the VERY end...), all my things don't work right=20 ::anymore.=20 ::> >> All apps like GnomeMeeting, the battery meter, etc appear to be=20 ::> >> completely messed up. For the most part, they run, but ::> none of the ::> >> words, etc are there! The battery meter, when I click=20 ::on it, only ::> >> shows the "Do Not Enter" ERROR box, no text and nothing=20 ::> else visible ::> >> - again, no words, etc. The same goes for GnomeMeeting. ::> Also when I ::> >> try to run the proccess display applet, nothing shows=20 ::up, just the ::> >> 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 ::> >> do I fix this?! ::> > ::> > GTK+ was updated recently and this sounds like what happens ::> when apps ::> > that use it get out of sync with it. You will have to recompile ::> > everything that uses GTK+. I suggest portupgraded. ::> > ::> > /me recently saw this himself with the gtk apps he uses=20 ::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=20 ::cause the build to fail, but it will not cause any lasting=20 ::damage to your ports tree, unless you have done=20 ::something exceptionally creative. Simply download the=20 ::gnome_upgrade.sh script and=20 ::run it, and pretend that you ran it in the first place.=20 ::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=20 ::probable. There are many possible valid GNOME configurations,=20 ::and even more invalid starting points. If the script fails,=20 ::follow the instructions in the error message to let the=20 ::FreeBSD GNOME team know about=20 ::the failure. :: ::The majority of build failures will be dependency-related=20 ::issues. One simple way to resolve the problem is to remove=20 ::the offending port, re-run gnome_upgrade.sh, and then=20 ::reinstall the port when the upgrade process is complete. :: :: :: ::_______________________________________________ ::freebsd-questions@freebsd.org mailing list=20 ::http://lists.freebsd.org/mailman/listinfo/free::bsd-questions :: ::To unsubscribe, send any mail to=20 ::"freebsd-questions-unsubscribe@freebsd.org" :: Thanks Mark - but I did run the gnome-upgrade.sh script provided off their site. It left a temp log file, which got erased when I rebooted. I'm wondering if I should try and run it again, and keep all the debug info this time? Maybe that would help me debug this problem... Has anyone else had this sort of...weird...glitch? Ralph