From owner-freebsd-questions@FreeBSD.ORG Sun Nov 21 03:56:36 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 C4A2416A4CF for ; Sun, 21 Nov 2004 03:56:36 +0000 (GMT) Received: from ecintweb.eldocomp.com (smtp.eldocomp.com [205.159.99.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18AF743D41 for ; Sun, 21 Nov 2004 03:56:36 +0000 (GMT) (envelope-from wbloom@eldocomp.com) Received: by ecintweb.eldocomp.com with XWall v3.29f ; Sat, 20 Nov 2004 20:56:35 -0700 From: William Bloom To: "freebsd-questions@freebsd.org" Date: Sat, 20 Nov 2004 20:56:32 -0700 X-Assembled-By: XWall v3.29f Message-ID: <41A011F0.6080409@eldocomp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Thunderbird 0.9_2 Stalls at Startup 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: Sun, 21 Nov 2004 03:56:37 -0000 I upgraded my FreeBSD/GNOME desktop from 5.2.1 to 5.3 early last week, refre= shed=20 my ports collection, upgraded from XFree86 to Xorg. I added the recommended= =20 libc_r/libpthread entries into libmap.conf for the sake of the already exist= ing=20 ports that had some library references to libc_r. All was well so far, no m= ajor=20 problems. I upgraded a few ports, including firefox. Again, this all worke= d=20 out albeit I was briefly stymied by the firefox Xvfb extension/theme=20 auto-registration issues that have been the cause of a few other postings in= =20 this list. But my luck turned sour when I upgraded my thunderbird port to 0.9_2. The n= ew=20 thunderbird would start, seemingly display the IMAP authentication panel=20 briefly, almost too fast to see, then churn its busy cursor until I killed i= t.=20 This behavior was repeatable even when I renamed my ~/.thunderbird directory= to=20 give thunderbird a clean slate, so the problem wasn't in my .thunderbird con= tents. Interestingly, the package from ftp.freebsd.org (5-stable) installed and ran= =20 fine. Being concerned that something might be fundamentally wrong with my=20 desktop build environment, I looked at the differences between the downloade= d=20 package and my build. What I discovered is that my own build of thunderbird had created a GNOME=20 component during the build (libmozgnome.so), which was installed in... =20 /usr/X11R6/lib/thunderbird/lib/thunderbird-0.9/components/ The downloaded package did -not- have this component. Experimentally, I del= eted=20 libmozgnome.so and found that the oddball startup-and-stall problem vanished= and=20 thunderbird has been working just fine ever since. I know I'm working with a thunderbird that's had a revision or so since the=20 package was built. I see from a brief perusal of the sources that the=20 libmozgnome.so component is only built under certain conditions (certain GNO= ME=20 libraries/features are checked and must all be present). I'm guessing that = the=20 downloadable package must either been built in the absence of one or more of= =20 these libraries -or- the port revision from which that package was built had= not=20 enabled GNOME component support. My GNOME ports were last brought up-to-dat= e=20 about six weeks ago. Also, I notice that the libmozgnome.so component=20 (toolkit/components/gnome in the thunderbird mozilla source tree) is fairly = new;=20 it showed up in version 0.8 (I never used that version). Anyone else seen this problem? Looks like the purpose of libmozgnome.so is to add support for GNOME VFS and= Gconf. Bill --=20 William Bloom (602) 604-3100 Eldorado Computing, Inc. 5353 North 16th Street, Suite 400 Phoenix, Az 85016 http://www.eldocomp.com -- CONFIDENTIALITY NOTICE -- This message is intended for the sole use of the individual and entity to wh= om it is addressed, and may contain information that is privileged, confiden= tial and exempt from disclosure under applicable law. If you are not the int= ended addressee, nor authorized to receive for the intended addressee, you a= re hereby notified that you may not use, copy, disclose or distribute to any= one the message or any information contained in the message. If you have rec= eived this message in error, please immediately advise the sender by reply e= mail, and delete the message. Thank you.