Can anyone else confirm that using Firefox 3 beta 5 through RC2 and the Linux iPrint client crashes apache2 on NW65sp7?

Facts:
Client: Ubuntu 8.04, Firefox 3 (beta 5, rc1, or rc2), iPrint 4.27
Server: Netware 6.5 sp7, IPPSRVR.NLM v4.00.12, APACHE2.NLM v2.00.59

Using the linux client and firefox and browsing to http://server/ipp and then clicking on a printer to install it crashes apache2.nlm (Apache_Worker ## Process) with (ippsrvr.nlm (Data Start)+3AA8) in the "Stack:" every time, instantly (abends, logged in abend.log). Also, firefox on the client hangs.

Using Firefox v2.0.0.13 does not crash the server or hang firefox.

I'd like to confirm that someone else can reproduce the problem before reporting it to Novell. Possibly using SLED instead of Ubuntu?

Or if this is already know and a fix is available can someone clue me in?

To install the iPrint client as a .deb package read: Using iPrint with Ubuntu | Novell User Communities

...And yes, I know FF3 is "BETA" but RC2 is all but complete and out the door.

Thanks.



Abend log:
************************************************** *******
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.07

Server CLI1 halted Tuesday, June 3, 2008 2:48:10.172 pm
Abend 1 on P00: Server-5.70.07: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 0000000C EBX = A8972038 ECX = 0000006F EDX = 726A0E90
ESI = A8971AA8 EDI = A8B36055 EBP = A8B35E28 ESP = A8B35E00
EIP = 863E3733 FLAGS = 00010206
863E3733 803800 CMP [EAX]=?, 00
EIP in LIBC.NLM at code start +00096733h
Access Location: 0x0000000C

The violation occurred while processing the following instruction:
863E3733 803800 CMP [EAX], 00
863E3736 89C7 MOV EDI, EAX
863E3738 89DE MOV ESI, EBX
863E373A 88CA MOV DL, CL
863E373C 743D JZ 863E377B
863E373E 89C0 MOV EAX, EAX
863E3740 89F8 MOV EAX, EDI
863E3742 83C701 ADD EDI, 00000001
863E3745 3810 CMP [EAX], DL
863E3747 752D JNZ 863E3776



Running process: Apache_Worker 23 Process
Thread Owned by NLM: APACHE2.NLM
Stack pointer: A8B3463C
OS Stack limit: A8B28FA0
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --A8B35E28 ?
--A8B36055 ?
-A8971AA8 (IPPSRVR.NLM|(Data Start)+3AA8)
--A8B36008 ?
A8963A39 (IPPSRVR.NLM|(Code Start)+DA39)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
-A8972038 (IPPSRVR.NLM|(Data Start)+4038)
--A8B36055 ?
-A8971AA8 (IPPSRVR.NLM|(Data Start)+3AA8)
--A8B36008 ?
--A8B37390 ?
A896278D (IPPSRVR.NLM|(Code Start)+C78D)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--A8B36008 ?
--A8B3600C ?
--6F6A6F64 ?
--6D74682E ?
--5F0A3B6C ?
--A87F6878 ?
--6F6A6F64 ?
--A8B35EA4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--6F643D39 ?
--622E6F6A ?
--28644979 ?
--3963355F ?
--760A3B29 ?
--5F207261 ?
--A8B35EAC ?
--FE300840 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A8B36048 ?
--72512250 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00320034 (SERVER.NLM|SetAllocFreeCheckFlag+284)
00300035 (SERVER.NLM|ProcessMonthOrdinalFormat+155)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
--6F37E6D0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000021 (LOADER.NLM|KernelAddressSpace+21)
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--75657571 ?
--6A2D6465 ?
--632D626F ?
--746E756F ?
--6E6F7361 ?
--626F6C73 ?
--54534373 ?
--5F454552 ?
--5F5F5F5F ?
--76D41040 ?
--9A9F5000 (DPLSV386.NLM|nwdp_getnotifyndsobjectname_1+BE30)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9A9F5000 (DPLSV386.NLM|nwdp_getnotifyndsobjectname_1+BE30)
00208402 (SERVER.NLM|kMutexUnlock+10A)
--7245C420 ?
--9A9F5000 (DPLSV386.NLM|nwdp_getnotifyndsobjectname_1+BE30)
--76D41040 ?
--0000006B (LOADER.NLM|KernelAddressSpace+6B)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8D8AB700 ?
--A8B36000 ?
--A8B36050 ?
--A8B36000 ?
--76D3B720 ?
8D2B3608 (NLMLIB.NLM|_GetServerInformation+1058)
--A8B36050 ?
--A8B35F1C ?
--494C4304 ?
--00000031 (LOADER.NLM|KernelAddressSpace+31)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--FFFFFFFF ?
--FFFFFFFF ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--72EE87E4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8D77F6E4 ?
--A8B35F80 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--0000006B (LOADER.NLM|KernelAddressSpace+6B)
8D9D65B1 (DS.NLM|MASVGetConnPartitionAccess+38)
--0000006B (LOADER.NLM|KernelAddressSpace+6B)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--8D77F6E0 ?
--72EE87E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--72EE8220 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--A8B35FC0 ?
--8D8AB700 ?
--A8B36000 ?
--0000000A (LOADER.NLM|KernelAddressSpace+A)

Additional Information:
The CPU encountered a problem executing code in LIBC.NLM. The problem may be in that module or in data passed to that module by a process owned by APACHE2.NLM.