Upgrade on PPC G5 system won't run but will on an Intel system

[Kok-Yong Tan]

On Apr 20, 2008, at 02:18, Kok-Yong Tan wrote:
> On Apr 20, 2008, at 02:07, Kok-Yong Tan wrote:
>> Where does wireshark write its error messages to?  I did a "sudo  
>> port -uRv upgrade wireshark" via MacPorts on a PowerPC G5 Mac OS  
>> 10.4.11 system and while it upgraded wireshark from 0.997 to 1.0  
>> successfully, wireshark will no longer start up its GUI under X- 
>> windows like it used to although it seems to be running without  
>> crashing (i.e., it seems to be running headless).  On the other  
>> hand, a similar command on a Intel-based Mac OS 10.4.11 system  
>> successfully resulted in an upgrade from 0.997 to 1.0.0 and also  
>> successfully runs under X-windows.  I'd like to find out what's  
>> making my PPC version go all coy on me and refuse to show its  
>> GUI... ;-)
>>
>
> Oh, I forgot to mention that I've already checked the DISPLAY  
> variable on the PPC machine in the xterm window that I'm trying to  
> run wireshark off of and it's already correctly set to ":0.0".


Something weird happened:  After attempting to start wireshark via  
both "wireshark" and "sudo wireshark" and waiting for over 3 minutes  
for it to show its GUI or send some output to the xterm I had started  
it from (my system load numbers are around 0.65), I forgot about it  
and left it running while I switched over to do some online research  
on my web browser.  Over twenty minutes later (I started it around  
2:05am and it didn't pop up until 2:29am!!!), the wireshark GUI  
suddenly popped up after first displaying the usual "loading" status  
bar.  And in the xterm it started from, I got these errors just as  
the status bar was moving across the "loading" window:

(wireshark:1036): Pango-WARNING **: Error loading GDEF table 28333

(wireshark:1036): Pango-WARNING **: Error loading GSUB table 28333

(wireshark:1036): Pango-WARNING **: Error loading GPOS table 28333

The above messages never showed up before but that was probably  
because I usually gave up after 5 minutes and aborted the startup by  
hitting control-C because wireshark used to start up instantly.  Then  
I shut down wireshark cleanly by quitting out of it and restarting  
it.  It started immediately this time around (less than 1 second  
between my typing "wireshark" and the GUI showing up). But it keeps  
giving me the same three error messages above although with different  
PIDs in place of the 1036 number above.  Anybody know what's going on  
here?  According to "port info pango", I have the following version  
of pango which got built using "sudo port -uRv upgrade wireshark":

pango 1.20.0, Revision 1, x11/pango (Variants: universal, no_X11)
http://www.pango.org

The goal of the Pango project is to provide an open-source framework  
for the layout and rendering of internationalized text.

Library Dependencies: glib2, XFree86, Xft2, cairo, fontconfig
Platforms: darwin
Maintainers: ryandesign at macports.org
--
Reality Artisans, Inc.            #   Network Wrangling and Delousing
P.O. Box 565, Gracie Station      #   Apple Certified Help Desk  
Specialist
New York, NY 10028-0019           #   Apple Consultants Network member
<http://www.realityartisans.com>  #   Apple Developer Connection member
(212) 369-4876 (Voice)            #   (212) 860-4325 (Fax)