Re: Suddenly lots processes exits signal 11 (core dumped)
On 4/26/2011 7:50 PM, Chris Hill wrote: [snip] tripel# echo p 2 0x0c * * | fdisk -f - /dev/da0 *** Working on device /dev/da0 *** fdisk: Class not found tripel# Try (note the single quotes): tripel# echo 'p 2 0x0c * *' | fdisk -f - /dev/da0 Just a hunch but perhaps the shell is globbing a filename. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE install freezes
Following up on my original post, I went back and tried to install 7.3-RELEASE. The install once again hung right around the time when the system would normally announce Timecounters tick every xxx msec. Since disabling ACPI and PnP doesn't seem to help, I'm wondering what might have changed between 6.x and 7.3 as it relates to the kernel bootstrapping process at this stage? I am actually netbooting this install, so I have the ability to compile a custom kernel to troubleshoot this further. I'd really like to install 8.0 on this hardware and get a few more years of life out of it. Thanks, Steve On Fri, 30 Apr 2010, Steve Bernacki wrote: Hi, I have an ancient Pentium II 350Mhz system that I've used as a home firewall for several years. I decided to try to upgrade it from 6.1 to 8.0 today, but I was unable to get the kernel to boot without freezing. The point at which it froze was: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Thinking it may be some ACPI related issue, I tried disabling ACPI in the kernel and from the boot prompt, but still no joy. I also tried fiddling with the PnP BIOS settings with no luck. Placing system into verbose logging mode, it gets as far as printing out: Device configuration finished. procfs registered And then freezes, right before it normally displays the Timecounters tick every xxx msec line. I have attached the full dmesg from the working 6.1 system. I know it's a shot in the dark, but does anyone have any ideas or suggestions as to what I could do to try to get this thing to boot? I've gotten many years of service out of this system, but I'd still like to squeeze out a few more. :) Thanks, Steve === 6.1 dmesg === Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006 r...@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = GenuineIntel Id = 0x665 Stepping = 5 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3 6,MMX,FXSR real memory = 268369920 (255 MB) avail memory = 253128704 (241 MB) kbd1 at kbdmux0 acpi0: 123456 AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xd3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 3.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf0 00-0xf00f at device 7.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 15 at device 7 .2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge at device 7.3 (no driver attached) pcib2: PCI-PCI bridge at device 11.0 on pci0 pci2: PCI bus on pcib2 fxp0: Intel 82557 Pro/100 Ethernet port 0xd000-0xd01f mem 0xd910-0xd9100fff,0xd7 00-0xd70f irq 11 at device 13.0 on pci2 miibus0: MII bus on fxp0 nsphy0: DP83840 10/100 media interface on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:a0:c9:1b:01:5c dpt0: DPT Caching SCSI RAID Controller port 0xd400-0xd41f irq 10 at device 14.0 on p ci2 dpt0: DPT PM2044W FW Rev. 07M1, 1 channel, 64 CCBs dpt0: [GIANT-LOCKED] fxp1: Intel 82559 Pro/100 Ethernet port 0xe400-0xe43f mem 0xd9301000-0xd9301fff,0xd9 00-0xd90f irq 15 at device 12.0 on pci0 miibus1: MII bus on fxp1 inphy0: i82555 10/100 media interface on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:50:bf:00:00:41 fxp2: Intel 82559 Pro/100 Ethernet port 0xe800-0xe83f mem 0xd930-0xd9300fff,0xd9 20-0xd92f irq 11 at device 13.0 on pci0 miibus2: MII bus on fxp2 inphy1: i82555 10/100 media interface on miibus2 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp2: Ethernet address: 00:50:bf:00:00:42 acpi_tz0: Thermal Zone on acpi0 fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port port
Re: 8.0-RELEASE install freezes
On Wed, 12 May 2010, Adam Vande More wrote: Try updating the BIOS, and tweaking settings there. Hi Adam, The BIOS is at it's latest version. It is an ancient system, so perhaps it's time to just retire the hardware, but I didn't want to give up without poking at it a bit more. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0-RELEASE install freezes
Hi, I have an ancient Pentium II 350Mhz system that I've used as a home firewall for several years. I decided to try to upgrade it from 6.1 to 8.0 today, but I was unable to get the kernel to boot without freezing. The point at which it froze was: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Thinking it may be some ACPI related issue, I tried disabling ACPI in the kernel and from the boot prompt, but still no joy. I also tried fiddling with the PnP BIOS settings with no luck. Placing system into verbose logging mode, it gets as far as printing out: Device configuration finished. procfs registered And then freezes, right before it normally displays the Timecounters tick every xxx msec line. I have attached the full dmesg from the working 6.1 system. I know it's a shot in the dark, but does anyone have any ideas or suggestions as to what I could do to try to get this thing to boot? I've gotten many years of service out of this system, but I'd still like to squeeze out a few more. :) Thanks, Steve === 6.1 dmesg === Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006 r...@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = GenuineIntel Id = 0x665 Stepping = 5 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3 6,MMX,FXSR real memory = 268369920 (255 MB) avail memory = 253128704 (241 MB) kbd1 at kbdmux0 acpi0: 123456 AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xd3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 3.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf0 00-0xf00f at device 7.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 15 at device 7 .2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge at device 7.3 (no driver attached) pcib2: PCI-PCI bridge at device 11.0 on pci0 pci2: PCI bus on pcib2 fxp0: Intel 82557 Pro/100 Ethernet port 0xd000-0xd01f mem 0xd910-0xd9100fff,0xd7 00-0xd70f irq 11 at device 13.0 on pci2 miibus0: MII bus on fxp0 nsphy0: DP83840 10/100 media interface on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:a0:c9:1b:01:5c dpt0: DPT Caching SCSI RAID Controller port 0xd400-0xd41f irq 10 at device 14.0 on p ci2 dpt0: DPT PM2044W FW Rev. 07M1, 1 channel, 64 CCBs dpt0: [GIANT-LOCKED] fxp1: Intel 82559 Pro/100 Ethernet port 0xe400-0xe43f mem 0xd9301000-0xd9301fff,0xd9 00-0xd90f irq 15 at device 12.0 on pci0 miibus1: MII bus on fxp1 inphy0: i82555 10/100 media interface on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:50:bf:00:00:41 fxp2: Intel 82559 Pro/100 Ethernet port 0xe800-0xe83f mem 0xd930-0xd9300fff,0xd9 20-0xd92f irq 11 at device 13.0 on pci0 miibus2: MII bus on fxp2 inphy1: i82555 10/100 media interface on miibus2 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp2: Ethernet address: 00:50:bf:00:00:42 acpi_tz0: Thermal Zone on acpi0 fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xcc000-0xccfff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A
Re: snapshot is corrupt
This happens to me from time to time on a few older (6.1) systems. Typically, re-running portsnap fetch clears the issue. Steve On 9/8/07, Jeffrey Goldberg [EMAIL PROTECTED] wrote: I just got the following when trying a portsnap. Any ideas? I really don't understand how portsnap works, so for me the error message isn't that useful. $ sudo portsnap fetch update Password: Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. Fetching snapshot tag from portsnap3.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Fri Sep 7 04:51:41 CDT 2007 to Sat Sep 8 05:50:59 CDT 2007. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 1285 patches. 102030405060708090100110120. ... 13014015016017018019020021022023 0240250260270280290300310320330. ... 34035036037038039040041042043044 0450460470480490500510520530540. ...550560570580590 done. Applying patches... done. Fetching 708 new ports or files... /usr/sbin/portsnap: cannot open e34b76c53bfd361a3defe2a9a884c0aa4f10da8b845ddf8e991fc419b3109f09.gz: No such file or directory snapshot is corrupt. $ Thanks, -j ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SpamAssassin and the nonexistent home directory.
Start spamd with -D (debug) on both servers to see where and how spamassassin is configuring itself. Chances are there is some subtle configuration variation that is causing this behavior. It's easy for this to happen given the fact that spamassassin reads through a number of directories for configuration information when it starts up. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Userland PPP MSS miscalculation?
I think that I've stumbled upon a miscalculation that userland-PPP makes when mssfixup is enabled and I wanted to run it by a larger audience before I submitted a problem report. By default, FreeBSD calculates the TCP MSS value of a new TCP connection by taking the MTU of the egress interface and subtracting 40 -- 20 for ip headers, and 20 for tcp headers. Thus, A TCP SYN packet exiting an interface with an MTU of 1500 will have an MSS of 1460. Well behaved TCP implementations seem to know that MSS is a value that does NOT include any TCP options; the number of bytes that TCP options consume are effectively subtracted from the agreed-upon MSS value. So, for a full packet (1500mtu/1460mss) with 12 bytes of TCP options, the maximum data payload size is 1448. 1448 (payload) + 12 (TCP options) + 20 (TCP headers) + 20 (IP headers) = 1500. In userland-PPP, the MSS value of an outgoing TCP SYN packet is calculated as such: tcpmss.c: line 73: [tcpmss.c,v 1.7.2.1] #define MAXMSS(mtu) ((mtu) - sizeof(struct ip) - sizeof(struct tcphdr) - 12) A change was made on 6/29/2004 to tcpmss.c to subtract 12 from the MAXMSS calculation (See http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ppp/tcpmss.c.diff?r1=1.6r2=1.7f=h. According to the PR report that caused the change (bin/32717), this was done to pad additional space for TCP options that might be present. The author, Koji Mori, presents a test case that involves connecting to www.netbsd.org, but I suspect that the bug was actually in NetBSD's MSS calculation, although I've not done any research to see if this is the case. By removing the -12 from the MAXMSS calculation and recompiling ppp, outgoing SYN packets on my PPPoE-connected system now have an MSS value of 1452, which works perfectly well. With the -12 included, the MSS is calculated as 1440. This works perfectly well of course, but it wastes 12 extra bytes that could be included in a packet's payload. Am I missing something here, or is my evaluation correct? If it is correct, I'll go ahead and submit a PR to revert the -12 change. Thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Font selection problem with GAIM 0.70 port
On Sat, 4 Oct 2003, Joe Marcus Clarke wrote: Works fine for me on two different systems. No one else has reported this yet. You said this is a new system, but did you migrate an old .gaimrc? Nope, I had gaim generate a fresh .gaim directory for me. What version of freetype2 do you have installed? I initially used the version that came with the XFree86.org 4.3.0 binary distribution, which appears to be 2.1.0. Today, I manually removed both this version of freetype2 and fontconfig, and installed the latest versions out of the the ports collection (freetype2-2.1.5_1 and fontconfig-2.2.90_3, respectively). Have you run fc-cache -f -v as root? Running fc-cache as root gives me: # fc-cache -f -v fc-cache: /usr/X11R6/lib/X11/fonts: caching, 0 fonts, 13 dirs fc-cache: /usr/X11R6/lib/X11/fonts/75dpi: caching, 397 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/misc: caching, 55 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/CID: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/local: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/util: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/encodings: caching, 0 fonts, 1 dirs fc-cache: /usr/X11R6/lib/X11/fonts/encodings/large: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/100dpi: caching, 397 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/cyrillic: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/Speedo: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/Type1: caching, 29 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/TTF: caching, 13 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/PEX: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/latin2: caching, 0 fonts, 2 dirs fc-cache: /usr/X11R6/lib/X11/fonts/latin2/100dpi: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/latin2/75dpi: caching, 0 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/TTF: caching, 13 fonts, 0 dirs fc-cache: /usr/X11R6/lib/X11/fonts/Type1: caching, 29 fonts, 0 dirs fc-cache: /home/steve/.fonts: skipping, no such directory fc-cache: succeeded Unfortunately, running a freshly built version of GAIM produces the same results as before. Perhaps part of my install was statically linked to an older version of the fontconfig libraries? Most of the ports were built using the XFree86.org bundled freetype2 and fontconfig; I'm not sure how that might play into this, as I'm not quite clear as to what system components use these libraries. I'd be glad to give you any additional information that you might be interested in; I'm stumped at this point. Thanks again, Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Font selection problem with GAIM 0.70 port
On Sun, 5 Oct 2003, Joe Marcus Clarke wrote: What versions of fontconfig and Xft do you have? I was using the version that came with the XFree86 4.3.0 binary distro, which was 2.1.0. I tried removing that manually and installing Xft-2.1.2 from the ports collection, but I am still seeing the same error with GAIM. Thanks, Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Font selection problem with GAIM 0.70 port
On Sun, 5 Oct 2003, Joe Marcus Clarke wrote: What about fontconfig? That's the important one. fontconfig version is fontconfig-2.2.90_3 from the ports collection; Xft-2.1.2 from the ports collection as well. Many of the X-windows related ports on this new system (gtk2, etc.) were built before I manually uninstalled the XFree86 4.3.0 binary release of freetype2 [2.1.0], fontconfig [2.2.90], and Xft [2.1.0] and installed the ports versions: freetype2-2.1.5_1 fontconfig-2.2.90_3 Xft-2.1.2 ...ugh, version number hell. :) Thanks, Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Font selection problem with GAIM 0.70 port
On Sun, 5 Oct 2003, Joe Marcus Clarke wrote: Do any other GTK-2 apps work? Do you have a ~/.gtkrc-2.0? The only other GTK2 app that I have installed is Xchat 2.0.5, and I've had no problems with it so far. And I have no ~/.gtkrc-2.0, so it's flying on system defaults. What's interesting is that if I go into GAIM preferences-fonts-use custom face, clicking on the Font button brings up the standard Select Font window that I'd expect the Conversation/Font Face button to bring up. Since I've not yet gotten the latter to work, though, I'm not sure what it's supposed to bring up. Thanks, Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Font selection problem with GAIM 0.70 port
When in a conversation window, clicking on the Font Face button causes gaim-0.70 to spew the following to stderr: ** (gaim:199): WARNING **: Couldn't load font fixed Medium Semi-Condensed 0 falling back to Sans Medium Semi-Condensed 0 ** (gaim:199): WARNING **: Couldn't load font Sans Medium Semi-Condensed 0 falling back to Sans 0 ** (gaim:199): WARNING **: All font failbacks failed ...at which point the program exits. Googling this error message points to an improperly configured freetype2 library or fontconfig configuration. However, as far as I can tell, there are no configuration problems on my system: fc-list spits out 30 a number of fonts, although none that start with Sans proper. This is a brand new system, so unfortunately I'm unsure if previous versions of GAIM have worked properly. System: FreeBSD 4.8-RELEASE + latest security patches XFree86 4.3.0 with all stock fonts Related ports: freetype-1.3.1_2 gettext-0.12.1 gtk-2.2.4_1 glib-2.2.3 pango-1.2.5 (from ports-current as of 10/1/2003) If anyone has any ideas, or can at least confirm that they are experiencing the same problem with this version of GAIM, I'd really appreciate it. Thanks, Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
